| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Stop using let_stmt twice | DJMcNab | 2019-01-27 | 1 | -43/+41 |
| | | |||||
| * | Make attrs be a child of the let statement | DJMcNab | 2019-01-26 | 1 | -6/+9 |
| | | |||||
| * | Support attributes on let statements | DJMcNab | 2019-01-26 | 1 | -20/+30 |
| | | |||||
| * | Struct literals should not be a `BlockLike::Block` | DJMcNab | 2019-01-26 | 1 | -1/+1 |
| | | |||||
| * | Support universal function call syntax in function calls | DJMcNab | 2019-01-24 | 1 | -0/+2 |
| | | |||||
| * | make token set a const-fn | Aleksey Kladov | 2019-01-19 | 1 | -4/+2 |
| | | |||||
| * | Improve parsing of incomplete field accesses in preparation for field completion | Florian Diebold | 2018-12-25 | 1 | -9/+7 |
| | | | | | | We need to be able to get the receiver even if there is no field name yet, and currently "a." wouldn't get parsed as a field name at all. This seems to help. | ||||
| * | Use a better way of skipping SEMIs | DJMcNab | 2018-12-20 | 1 | -6/+6 |
| | | |||||
| * | Support a blank expression before a semicolon | DJMcNab | 2018-12-20 | 1 | -0/+6 |
| | | |||||
| * | Fix missing DOTDOTEQs | DJMcNab | 2018-12-20 | 1 | -3/+3 |
| | | |||||
| * | Add tests and only traverse in the crates directory | DJMcNab | 2018-12-19 | 1 | -2/+6 |
| | | |||||
| * | Move is_block to lower in the call tree | DJMcNab | 2018-12-19 | 1 | -44/+33 |
| | | |||||
| * | Revert "Revert to f6f7c5" | DJMcNab | 2018-12-19 | 1 | -13/+26 |
| | | | | | | | This approach is correct, but it needs an addition to Restrictions too This reverts commit ad00d0c8a5f64142e6636e8b048204c8f8982f4a. | ||||
| * | Revert to f6f7c5 | DJMcNab | 2018-12-19 | 1 | -26/+13 |
| | | |||||
| * | Fix expression parsing by bailing out upon a macro block being found | DJMcNab | 2018-12-19 | 1 | -14/+12 |
| | | | | | | | TODO: Fix this when the block like macro is in expression position E.g. `test(test!{})` currently parses | ||||
| * | Possibly fix #225 | DJMcNab | 2018-12-19 | 1 | -15/+30 |
| | | |||||
| * | Fix at_ts doc comment | DJMcNab | 2018-12-19 | 1 | -1/+1 |
| | | |||||
| * | Fix parsing of inclusive ranges (#214) | DJMcNab | 2018-12-19 | 1 | -2/+2 |
| | | | | | I'm not certain that this is correct, so extra eyes would be good | ||||
| * | Fixed cast expression parsing in ra_syntax. | Roland Ruckerbauer | 2018-12-17 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | | | | | | | | | The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes all plus sign after path types as extra. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`. | ||||
| * | grand module rename | Aleksey Kladov | 2018-12-08 | 1 | -0/+455 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |