aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/tests/data/parser/inline
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix parsing of inclusive ranges (#214)DJMcNab2018-12-192-27/+65
| | | | I'm not certain that this is correct, so extra eyes would be good
* Fixed cast expression parsing in ra_syntax.Roland Ruckerbauer2018-12-172-6/+48
| | | | | | | | | | | | | | | | | | | | | | 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()`.
* Update use path testDJMcNab2018-12-052-74/+2
|
* Improve/add the use_item documentationDJMcNab2018-12-0510-0/+485
|
* rename ROOT -> SOURCE_FILEAleksey Kladov2018-11-07113-113/+113
|
* grammar: for predicates in whereAleksey Kladov2018-11-052-0/+62
| | | | closes #191
* Support leading pipe in match armsDaniel McNab2018-10-032-12/+56
|
* support 2018 pathsAleksey Kladov2018-09-292-0/+16
|
* generate testsuite for impl_typecsmoe2018-09-262-0/+83
|
* rename all thingsAleksey Kladov2018-09-16219-0/+5401