aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_parser/src
Commit message (Collapse)AuthorAgeFilesLines
* Correctly parse <_> paths in patternsAleksey Kladov2020-06-091-2/+4
| | | | closes #3659
* Minor, use `T!`Aleksey Kladov2020-06-092-2/+2
|
* Update crates/ra_parser/src/grammar/items.rsAleksey Kladov2020-06-091-2/+1
|
* Parse default unsafe fnAvi Dessauer2020-06-081-1/+7
|
* Move default const test out of lineAvi Dessauer2020-06-041-10/+0
|
* Address reviewAvi Dessauer2020-06-041-5/+4
|
* Parse default unsafe & default constAvi Dessauer2020-06-041-1/+25
|
* Update a comment for the new source organizationNelson Elhage2020-06-011-3/+4
|
* Support raw_ref_op's raw reference operatorrobojumper2020-05-281-1/+15
|
* Shrink ra_parser::Event from 32 bytes to 16 bytesSimon Vandel Sillesen2020-05-162-2/+2
| | | | This boxes the Error variant with the assumption that it is rarely constructed
* Fix parsing of blocks without `{`Aleksey Kladov2020-05-026-37/+29
|
* Cleanup inline testsAleksey Kladov2020-05-021-2/+4
|
* Introduce EffectExprAleksey Kladov2020-05-024-25/+22
|
* Revert "Merge #4233"Aleksey Kladov2020-05-022-3/+4
| | | | | This reverts commit a5f2b16366f027ad60c58266a66eb7fbdcbda9f9, reversing changes made to c96b2180c1c4206a0a98c280b4d30897eb116336.
* Remove dead code, which elaborately pretends to be aliveAleksey Kladov2020-04-302-4/+3
|
* Merge #4227bors[bot]2020-04-301-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4227: Report invalid, nested, multi-segment crate-paths r=matklad a=djrenren There was a bug in the previous path-validating code that didn't detect multi-segment paths that started with `crate`. ```rust // Successfully reported use foo::{crate}; // BUG: was not being reported use foo::{crate::bar}; ``` This was due to my confusion about path-associativity. That is, the path with no qualifier is the innermost path, not the outermost. I've updated the code with a lot of comments to explain what's going on. This bug was discovered when I found an erroneous `ok` test which I reported here: https://github.com/rust-analyzer/rust-analyzer/issues/4226 This test now fails and has been modified, hopefully in the spirit of the original test, to be correct. Sorry about submitting the bug in the first place! Co-authored-by: John Renner <[email protected]>
| * Report invalid, nested, multi-segment crate-pathsJohn Renner2020-04-301-1/+1
| | | | | | | | | | | | | | | | | | | | Specifically, things like: use foo::{crate::bar}; Are now being caught, when before we only caught: use foo::{crate};
* | Special-case try macro_rulesEdwin Cheng2020-04-301-0/+11
|/
* Special-case try macro to better support 2015 editionAleksey Kladov2020-04-301-0/+16
|
* Align grammar for record patterns and literalsAleksey Kladov2020-04-111-27/+23
| | | | | | The grammar now looks like this [name_ref :] pat
* Remove dead codeAleksey Kladov2020-04-111-7/+4
|
* Make records grammar more orthogonalAleksey Kladov2020-04-111-12/+25
| | | | | | | | | | | | We used name [: expr] grammar before, now it is [name :] expr which makes things simpler
* Rename some tokensAleksey Kladov2020-04-103-319/+33
|
* Scale token generation backAleksey Kladov2020-04-101-0/+6
|
* Parse correctly fn f<T>() where T: Fn() -> u8 + Send {}Luca Barbieri2020-04-091-1/+1
| | | | | We used to parse it as T: Fn() -> (u8 + Send), which is different from the rustc behavior of T: (Fn() -> u8) + Send
* Provide more complete AST accessors to support usage in rustcLuca Barbieri2020-04-091-1/+5
|
* Add L_DOLLAR for TYPE_RECOVERY_SETEdwin Cheng2020-04-081-1/+1
|
* Macro patterns are not confused with expressions.Aleksey Kladov2020-04-032-2/+3
| | | | | | | | | | | We treat macro calls as expressions (there's appropriate Into impl), which causes problem if there's expresison and non-expression macro in the same node (like in the match arm). We fix this problem by nesting macor patterns into another node (the same way we nest path into PathExpr or PathPat). Ideally, we probably should add a similar nesting for macro expressions, but that needs some careful thinking about macros in blocks: `{ am_i_expression!() }`.
* CleanupsAleksey Kladov2020-04-032-14/+13
|
* Fix parsing lambdas with return typeAleksey Kladov2020-03-251-7/+13
| | | | | | | We should eat only a single block, and not whatever larger expression may start with a block. closes #3721
* Support arbitrary discriminantsAleksey Kladov2020-03-201-4/+6
| | | | Closes #3661
* Better fix for stuck parser?Florian Diebold2020-03-161-3/+3
|
* Get tests workingFlorian Diebold2020-03-161-2/+2
|
* Parse variadics correctlyAleksey Kladov2020-03-131-11/+33
| | | | closes #3571
* Move verbose tests out of lineAleksey Kladov2020-03-131-20/+2
|
* Fix parsing of stement-ish binary expressionsAleksey Kladov2020-03-111-2/+8
| | | | closes #3512
* Implement concat macroEdwin Cheng2020-03-031-1/+1
|
* Rename ast::ImplBlock -> ast::ImplDefAleksey Kladov2020-02-294-7/+7
|
* Parse attr in rhs of let stmtsEdwin Cheng2020-02-281-1/+2
|
* Fix dat commentVeetaha2020-02-221-1/+1
|
* More manual clippy fixesKirill Bulatov2020-02-182-3/+3
|
* Run cargo +nightly fix --clippy -Z unstable-optionsKirill Bulatov2020-02-182-5/+3
|
* Add test for unnamed argument in function pointerHan Mertens2020-02-121-0/+3
|
* Support unnamed arguments in function pointersHan Mertens2020-02-121-1/+1
| | | | Fixes #3089
* Address review commentsMatthew Jasper2020-02-101-7/+8
|
* Add or- and parenthesized-patternsMatthew Jasper2020-02-094-14/+62
|
* Rename add import assistKirill Bulatov2020-02-071-1/+1
|
* Merge #3047bors[bot]2020-02-071-9/+9
|\ | | | | | | | | | | | | | | | | | | | | | | 3047: Update async unsafe fn ordering in parser r=matklad a=kiljacken As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: `async unsafe fn` and not `unsafe async fn`. This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering. Fixes #3025 Co-authored-by: Emil Lauridsen <[email protected]>
| * Update async unsafe fn ordering.Emil Lauridsen2020-02-071-9/+9
| | | | | | | | | | | | | | | | | | | | As of rust-lang/rust#61319 the correct order for functions that are both unsafe and async is: `async unsafe fn` and not `unsafe async fn`. This commit updates the parser tests to reflect this, and corrects parsing behavior to accept the correct ordering. Fixes #3025
* | PR tweaksToby Dimmick2020-02-073-21/+18
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 15:26:41 +0000