aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/grammar
Commit message (Collapse)AuthorAgeFilesLines
* Improve parsing of incomplete field accesses in preparation for field completionFlorian Diebold2018-12-251-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.
* Fix where clauses using fully qualified path syntaxDJMcNab2018-12-211-1/+6
|
* Fix parsing of contextual_keyword unionDJMcNab2018-12-201-1/+1
|
* Use a better way of skipping SEMIsDJMcNab2018-12-201-6/+6
|
* Support a blank expression before a semicolonDJMcNab2018-12-201-0/+6
|
* Fix the tests and fix the precommit hookDJMcNab2018-12-206-9/+9
|
* Fix missing DOTDOTEQsDJMcNab2018-12-201-3/+3
|
* Don't require a command before EQ in a where clauseDJMcNab2018-12-201-1/+1
|
* Simplify NO_BLOCK testingDJMcNab2018-12-202-11/+3
|
* Fix ambiguity with if breakDJMcNab2018-12-202-5/+21
| | | | Brought up by #290
* Add tests and only traverse in the crates directoryDJMcNab2018-12-192-2/+7
|
* Move is_block to lower in the call treeDJMcNab2018-12-192-54/+43
|
* Revert "Revert to f6f7c5"DJMcNab2018-12-192-19/+36
| | | | | | This approach is correct, but it needs an addition to Restrictions too This reverts commit ad00d0c8a5f64142e6636e8b048204c8f8982f4a.
* Fix handling of structs in match armsDJMcNab2018-12-191-1/+1
|
* Revert to f6f7c5DJMcNab2018-12-192-36/+19
|
* Fix expression parsing by bailing out upon a macro block being foundDJMcNab2018-12-191-14/+12
| | | | | | TODO: Fix this when the block like macro is in expression position E.g. `test(test!{})` currently parses
* Possibly fix #225DJMcNab2018-12-192-21/+40
|
* Fix at_ts doc commentDJMcNab2018-12-191-1/+1
|
* Fix parsing of inclusive ranges (#214)DJMcNab2018-12-192-4/+8
| | | | 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-9/+18
| | | | | | | | | | | | | | | | | | | | | | 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 renameAleksey Kladov2018-12-083-184/+0
|
* Use json comparison code from cargo for heavy testsFlorian Diebold2018-12-061-1/+1
|
* Improve/add the use_item documentationDJMcNab2018-12-051-1/+54
|
* Complete paths after ::Aleksey Kladov2018-11-212-2/+2
|
* rename ROOT -> SOURCE_FILEAleksey Kladov2018-11-071-1/+1
|
* grammar: fix where clause parsingAleksey Kladov2018-11-061-1/+5
| | | | closes #205
* reduce code duplicationAleksey Kladov2018-11-052-21/+19
|
* grammar: for predicates in whereAleksey Kladov2018-11-052-35/+67
| | | | closes #191
* clippy: Use if lets and remove redundant returnsAlan Du2018-10-183-10/+6
|
* Cargo FormatJeremy A. Kolb2018-10-1610-117/+137
| | | | Run `cargo fmt` and ignore generated files
* Parse crate paths in expressionsAleksey Kladov2018-10-151-1/+1
|
* Run cargo fixAleksey Kladov2018-10-151-1/+1
|
* Support leading pipe in match armsDaniel McNab2018-10-031-0/+3
|
* support 2018 pathsAleksey Kladov2018-09-291-3/+5
|
* generate testsuite for impl_typecsmoe2018-09-261-5/+5
|
* parse impl typecsmoe2018-09-251-10/+16
|
* reject impl keyword in impl headercsmoe2018-09-241-2/+10
|
* rename all thingsAleksey Kladov2018-09-1615-0/+2720