Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Fix expression parsing by bailing out upon a macro block being found | DJMcNab | 2018-12-19 | 1 | -3/+0 | |
| | | | | | | TODO: Fix this when the block like macro is in expression position E.g. `test(test!{})` currently parses | |||||
* | Fix parsing of inclusive ranges (#214) | DJMcNab | 2018-12-19 | 4 | -33/+150 | |
| | | | | I'm not certain that this is correct, so extra eyes would be good | |||||
* | Add a test to ensure that we can parse each file | DJMcNab | 2018-12-19 | 1 | -2/+43 | |
| | | | | Note that this has a non-spurious failure in ra_analysis/src/mock_analysis | |||||
* | Fixed cast expression parsing in ra_syntax. | Roland Ruckerbauer | 2018-12-17 | 2 | -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()`. | |||||
* | rename Edit to TextEdit and AtomEdit to AtomTextEdit | Bernardo | 2018-12-11 | 1 | -19/+19 | |
| | ||||||
* | Update use path test | DJMcNab | 2018-12-05 | 2 | -74/+2 | |
| | ||||||
* | Improve/add the use_item documentation | DJMcNab | 2018-12-05 | 10 | -0/+485 | |
| | ||||||
* | rename ROOT -> SOURCE_FILE | Aleksey Kladov | 2018-11-07 | 177 | -177/+177 | |
| | ||||||
* | Rename File -> SourceFileNode | Aleksey Kladov | 2018-11-07 | 1 | -2/+2 | |
| | ||||||
* | grammar: fix where clause parsing | Aleksey Kladov | 2018-11-06 | 2 | -0/+30 | |
| | | | | closes #205 | |||||
* | grammar: for predicates in where | Aleksey Kladov | 2018-11-05 | 2 | -0/+62 | |
| | | | | closes #191 | |||||
* | Cargo Format | Jeremy A. Kolb | 2018-10-16 | 1 | -5/+4 | |
| | | | | Run `cargo fmt` and ignore generated files | |||||
* | Parse crate paths in expressions | Aleksey Kladov | 2018-10-15 | 2 | -0/+44 | |
| | ||||||
* | Attach comments smartly | Aleksey Kladov | 2018-10-08 | 2 | -6/+6 | |
| | ||||||
* | Support leading pipe in match arms | Daniel McNab | 2018-10-03 | 2 | -12/+56 | |
| | ||||||
* | support 2018 paths | Aleksey Kladov | 2018-09-29 | 2 | -0/+16 | |
| | ||||||
* | generate testsuite for impl_type | csmoe | 2018-09-26 | 4 | -8/+89 | |
| | ||||||
* | parse impl type | csmoe | 2018-09-25 | 2 | -47/+28 | |
| | ||||||
* | add test for impl recovery | csmoe | 2018-09-24 | 2 | -0/+70 | |
| | ||||||
* | rename all things | Aleksey Kladov | 2018-09-16 | 372 | -0/+12664 | |