Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Move default const test out of line | Avi Dessauer | 2020-06-04 | 2 | -0/+47 |
| | |||||
* | Update test data | Aleksey Kladov | 2020-05-02 | 43 | -4103/+3976 |
| | |||||
* | Validate uses of self and super | John Renner | 2020-05-01 | 2 | -26/+1 |
| | |||||
* | Convert tests to text-size | Aleksey Kladov | 2020-04-25 | 68 | -9435/+9435 |
| | |||||
* | Align grammar for record patterns and literals | Aleksey Kladov | 2020-04-11 | 2 | -12/+16 |
| | | | | | | The grammar now looks like this [name_ref :] pat | ||||
* | Rename some tokens | Aleksey Kladov | 2020-04-10 | 48 | -497/+497 |
| | |||||
* | Parse correctly fn f<T>() where T: Fn() -> u8 + Send {} | Luca Barbieri | 2020-04-09 | 2 | -0/+62 |
| | | | | | We used to parse it as T: Fn() -> (u8 + Send), which is different from the rustc behavior of T: (Fn() -> u8) + Send | ||||
* | Migrate tests .txt -> .rast | veetaha | 2020-04-06 | 67 | -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. | ||||
* | Attach doc-comment to declaration if there are newlines in between | Leander Tentrup | 2020-03-31 | 2 | -0/+20 |
| | | | | This commit changes the parser to attach doc-comments to the corresponding declaration in case there are newlines in between the doc-comment and the declaration. | ||||
* | Parse variadics correctly | Aleksey Kladov | 2020-03-13 | 3 | -1/+140 |
| | | | | closes #3571 | ||||
* | Move verbose tests out of line | Aleksey Kladov | 2020-03-13 | 4 | -0/+373 |
| | |||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 3 | -3/+3 |
| | |||||
* | Rework value parameter parsing | Toby Dimmick | 2020-02-06 | 2 | -97/+61 |
| | | | | | | | - `Fn__(...)` parameters with idents/patterns no longer parse - Trait function parameters with arbitrary patterns parse - Trait function parameters without idents/patterns no longer parse - `fn(...)` parameters no longer parse with patterns other than a single ident | ||||
* | Use name instead of ident for macro 2.0 sytnax | Edwin Cheng | 2019-12-22 | 1 | -2/+4 |
| | |||||
* | Add macro 2.0 support in parser | Edwin Cheng | 2019-12-21 | 2 | -0/+189 |
| | |||||
* | Introduce dedicated AST node for union | Aleksey Kladov | 2019-11-25 | 1 | -1/+1 |
| | | | | | | | | | | Although structs and unions have the same syntax and differ only in the keyword, re-using the single syntax node for both of them leads to confusion in practice, and propagates further down the hir in an upleasent way. Moreover, static and consts also share syntax, but we use different nodes for them. | ||||
* | Fix parsing of "postfix" range expressions. | Geoffry Song | 2019-11-15 | 4 | -0/+91 |
| | | | | | | | | | | Right now they are handled in `postfix_dot_expr`, but that doesn't allow it to correctly handle precedence. Integrate it more tightly with the Pratt parser instead. Also includes a drive-by fix for parsing `match .. {}`. Fixes #2242. | ||||
* | fix parsing of for loops inside expressions | Aleksey Kladov | 2019-10-28 | 2 | -0/+106 |
| | | | | closes #2051 | ||||
* | Move tests around | Geoffry Song | 2019-10-06 | 2 | -0/+104 |
| | |||||
* | Parse correct AttrInput | uHOOCCOOHu | 2019-09-30 | 11 | -314/+423 |
| | |||||
* | Support loop as argument | kjeremy | 2019-09-20 | 2 | -0/+64 |
| | |||||
* | don't confuse macro with != | Aleksey Kladov | 2019-09-20 | 2 | -0/+69 |
| | | | | closes #1871 | ||||
* | Merge #1848 | bors[bot] | 2019-09-15 | 1 | -1/+2 |
|\ | | | | | | | | | | | | | | | | | | | | | | | 1848: Parse `..` as a full pattern r=matklad a=ecstatic-morse Resolves #1479. This PR implements [RFC 2707](https://github.com/rust-lang/rfcs/pull/2707) in the parser. It introduces a new `DotDotPat` AST node modeled on `PlaceholderPat` and changes the parsing of tuple and slice patterns to conform to the RFC. Notably, this PR does *not* change the resulting AST when `..` appears in a struct pattern (e.g. `Struct { a, b: c, .. }`). I *think* this is the behavior mandated by RFC 2707, but someone should confirm this. Co-authored-by: Dylan MacKenzie <[email protected]> | ||||
| * | Bless old tests containing a `..` pattern | Dylan MacKenzie | 2019-09-15 | 1 | -1/+2 |
| | | |||||
* | | Add tests for underscores in `const` and `static` items | Dylan MacKenzie | 2019-09-15 | 2 | -38/+57 |
|/ | |||||
* | add a jointness parser tests | Aleksey Kladov | 2019-09-10 | 2 | -0/+55 |
| | | | | cc https://github.com/rust-lang/rust/issues/64242 | ||||
* | WIP: switch to fully decomposed tokens internally | Aleksey Kladov | 2019-09-10 | 2 | -0/+131 |
| | |||||
* | Fix outer doc-comments of `macro_rules` | uHOOCCOOHu | 2019-09-09 | 2 | -0/+42 |
| | |||||
* | update test data | Aleksey Kladov | 2019-09-02 | 30 | -3585/+3676 |
| | |||||
* | rename struct -> record, pos -> tuple | Aleksey Kladov | 2019-08-23 | 10 | -39/+39 |
| | |||||
* | fix test position | bravomikekilo | 2019-08-14 | 2 | -0/+84 |
| | |||||
* | Fix parser tests according to review | Evgenii P | 2019-08-08 | 2 | -0/+498 |
| | |||||
* | move syntax tests to unit tests | Aleksey Kladov | 2019-07-24 | 102 | -0/+7864 |