Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Reame PlaceholderType -> InferType | Aleksey Kladov | 2020-07-31 | 2 | -2/+2 |
| | |||||
* | Finalize impl Grammar | Aleksey Kladov | 2020-07-30 | 14 | -14/+14 |
| | |||||
* | Finalize Trait grammar | Aleksey Kladov | 2020-07-30 | 6 | -9/+9 |
| | |||||
* | Finalize const&static grammar | Aleksey Kladov | 2020-07-30 | 3 | -3/+3 |
| | |||||
* | Rename EnumVariant -> Variant | Aleksey Kladov | 2020-07-30 | 3 | -6/+6 |
| | |||||
* | Rename EnumDef -> Enum | Aleksey Kladov | 2020-07-30 | 3 | -3/+3 |
| | |||||
* | Rename StructDef -> Struct | Aleksey Kladov | 2020-07-30 | 11 | -20/+20 |
| | |||||
* | Finalize union grammar | Aleksey Kladov | 2020-07-30 | 1 | -2/+2 |
| | |||||
* | Rename FieldDef -> Field | Aleksey Kladov | 2020-07-30 | 8 | -27/+27 |
| | |||||
* | Rename RecordLit -> RecordExpr | Aleksey Kladov | 2020-07-30 | 5 | -24/+24 |
| | |||||
* | Rename TypeParamList -> GenericParamList | Aleksey Kladov | 2020-07-30 | 15 | -22/+22 |
| | |||||
* | Rename TypeAliasDef -> TypeAlias | Aleksey Kladov | 2020-07-30 | 29 | -42/+42 |
| | |||||
* | Rename FnDef -> Fn | Aleksey Kladov | 2020-07-30 | 104 | -123/+123 |
| | |||||
* | Update tests | Aleksey Kladov | 2020-07-30 | 6 | -17/+17 |
| | |||||
* | Update tests | Aleksey Kladov | 2020-07-30 | 1 | -1/+1 |
| | |||||
* | Update tests | Aleksey Kladov | 2020-07-30 | 1 | -4/+4 |
| | |||||
* | Update tests | Aleksey Kladov | 2020-07-30 | 19 | -20/+20 |
| | |||||
* | Add example of old trait object syntax | Matthew Jasper | 2020-06-11 | 2 | -1/+38 |
| | |||||
* | Move complex inline test to own file | Matthew Jasper | 2020-06-11 | 2 | -267/+1 |
| | |||||
* | Separating parsing of `for` in predicates and types | Matthew Jasper | 2020-06-10 | 4 | -273/+372 |
| | |||||
* | Correctly parse <_> paths in patterns | Aleksey Kladov | 2020-06-09 | 2 | -0/+39 |
| | | | | closes #3659 | ||||
* | Parse default unsafe fn | Avi Dessauer | 2020-06-08 | 2 | -0/+43 |
| | |||||
* | Move default const test out of line | Avi Dessauer | 2020-06-04 | 2 | -47/+0 |
| | |||||
* | Update tests | Avi Dessauer | 2020-06-04 | 4 | -0/+66 |
| | |||||
* | Support raw_ref_op's raw reference operator | robojumper | 2020-05-28 | 2 | -44/+134 |
| | |||||
* | Fix parsing of blocks without `{` | Aleksey Kladov | 2020-05-02 | 2 | -24/+0 |
| | |||||
* | Cleanup inline tests | Aleksey Kladov | 2020-05-02 | 8 | -30/+59 |
| | |||||
* | Update test data | Aleksey Kladov | 2020-05-02 | 101 | -4938/+4759 |
| | |||||
* | Merge #4227 | bors[bot] | 2020-04-30 | 2 | -25/+26 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-paths | John Renner | 2020-04-30 | 2 | -25/+26 |
| | | | | | | | | | | | | | | | | | | | | Specifically, things like: use foo::{crate::bar}; Are now being caught, when before we only caught: use foo::{crate}; | ||||
* | | Special-case try macro_rules | Edwin Cheng | 2020-04-30 | 2 | -0/+28 |
|/ | |||||
* | Special-case try macro to better support 2015 edition | Aleksey Kladov | 2020-04-30 | 2 | -0/+36 |
| | |||||
* | Convert tests to text-size | Aleksey Kladov | 2020-04-25 | 158 | -9773/+9773 |
| | |||||
* | Align grammar for record patterns and literals | Aleksey Kladov | 2020-04-11 | 3 | -21/+25 |
| | | | | | | The grammar now looks like this [name_ref :] pat | ||||
* | Make records grammar more orthogonal | Aleksey Kladov | 2020-04-11 | 1 | -4/+10 |
| | | | | | | | | | | | | We used name [: expr] grammar before, now it is [name :] expr which makes things simpler | ||||
* | Rename some tokens | Aleksey Kladov | 2020-04-10 | 110 | -386/+386 |
| | |||||
* | Migrate tests .txt -> .rast | veetaha | 2020-04-06 | 158 | -0/+0 |
| | | | | | | | | The sytax tree output files now use .rast extension (rust-analyzer syntax tree or rust abstract syntax tree (whatever)). This format has a editors/code/ra_syntax_tree.tmGrammar.json declaration that supplies nice syntax highlighting for .rast files. | ||||
* | Macro patterns are not confused with expressions. | Aleksey Kladov | 2020-04-03 | 1 | -10/+11 |
| | | | | | | | | | | | 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!() }`. | ||||
* | Fix parsing lambdas with return type | Aleksey Kladov | 2020-03-25 | 2 | -0/+46 |
| | | | | | | | We should eat only a single block, and not whatever larger expression may start with a block. closes #3721 | ||||
* | Support arbitrary discriminants | Aleksey Kladov | 2020-03-20 | 2 | -0/+31 |
| | | | | Closes #3661 | ||||
* | Parse variadics correctly | Aleksey Kladov | 2020-03-13 | 2 | -2/+4 |
| | | | | closes #3571 | ||||
* | Move verbose tests out of line | Aleksey Kladov | 2020-03-13 | 8 | -387/+45 |
| | |||||
* | Fix parsing of stement-ish binary expressions | Aleksey Kladov | 2020-03-11 | 2 | -0/+41 |
| | | | | closes #3512 | ||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 15 | -13/+13 |
| | |||||
* | Parse attr in rhs of let stmts | Edwin Cheng | 2020-02-28 | 2 | -7/+35 |
| | |||||
* | Run cargo test | Han Mertens | 2020-02-12 | 1 | -0/+26 |
| | |||||
* | Run cargo xtask codegen | Han Mertens | 2020-02-12 | 1 | -0/+1 |
| | |||||
* | Address review comments | Matthew Jasper | 2020-02-10 | 2 | -7/+58 |
| | |||||
* | Update tests for or-patterns | Matthew Jasper | 2020-02-09 | 4 | -60/+184 |
| | |||||
* | Merge #3047 | bors[bot] | 2020-02-07 | 2 | -4/+4 |
|\ | | | | | | | | | | | | | | | | | | | | | | | 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]> |