aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/test_data/parser/inline
Commit message (Collapse)AuthorAgeFilesLines
* Introduce dedicated AST node for unionAleksey Kladov2019-11-251-2/+2
| | | | | | | | | | 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.
* Merge #1951bors[bot]2019-10-082-0/+46
|\ | | | | | | | | | | | | | | | | | | | | | | | | 1951: Lower the precedence of the `as` operator. r=matklad a=goffrie Previously, the `as` operator was being parsed like a postfix expression, and therefore being given the highest possible precedence. That caused it to bind more tightly than prefix operators, which it should not. Instead, parse it somewhat like a normal binary expression with some special-casing. Fixes #1851. Co-authored-by: Geoffry Song <[email protected]>
| * Move tests aroundGeoffry Song2019-10-066-141/+89
| |
| * Lower the precedence of the `as` operator.Geoffry Song2019-10-034-43/+141
| | | | | | | | | | | | | | Previously, the `as` operator was being parsed like a postfix expression, and therefore being given the highest possible precedence. That caused it to bind more tightly than prefix operators, which it should not. Instead, parse it somewhat like a normal binary expression with some special-casing.
* | Fix parsing of block expressions in "forbid_structs" contexts.Geoffry Song2019-10-038-43/+216
|/ | | | | | Forbidding block expressions entirely is too strict; instead, we should only forbid them in contexts where we are parsing an optional RHS (i.e. the RHS of a range expression).
* Parse correct AttrInputuHOOCCOOHu2019-09-3014-200/+254
|
* Add indexing to record_field_patkjeremy2019-09-202-0/+79
|
* Merge #1848bors[bot]2019-09-156-4/+489
|\ | | | | | | | | | | | | | | | | | | | | | | 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]>
| * Generate `dot_dot_test`Dylan MacKenzie2019-09-152-0/+481
| |
| * Bless old tests containing a `..` patternDylan MacKenzie2019-09-154-4/+8
| |
* | Add tests for underscores in `const` and `static` itemsDylan MacKenzie2019-09-151-0/+21
| |
* | Allow an underscore as the identifier in `const` itemsDylan MacKenzie2019-09-151-0/+1
|/
* update test dataAleksey Kladov2019-09-0298-3944/+4095
|
* Generate and bless testsDylan MacKenzie2019-08-246-85/+132
|
* rename struct -> record, pos -> tupleAleksey Kladov2019-08-2318-59/+59
|
* Add test for nested box patternDylan MacKenzie2019-08-222-12/+49
|
* Merge #1685bors[bot]2019-08-152-0/+45
|\ | | | | | | | | | | | | | | 1685: fix error of RangeFrom in for-loop r=DJMcNab a=bravomikekilo fix [issue-1542](https://github.com/rust-analyzer/rust-analyzer/issues/1542) @matklad Co-authored-by: bravomikekilo <[email protected]>
| * fix test positionbravomikekilo2019-08-144-113/+45
| |
| * fix testbravomikekilo2019-08-141-2/+2
| |
| * fix error of RangeFrom in for-loopbravomikekilo2019-08-142-0/+113
| |
* | Merge #1676bors[bot]2019-08-142-1/+83
|\ \ | |/ |/| | | | | | | | | | | 1676: Fix for<'lifetime> for types specified by path r=matklad a=eupn Fixes #1467. Co-authored-by: Evgenii P <[email protected]>
| * Fix for<'lifetime> for types specified by pathEvgenii P2019-08-112-1/+83
| |
* | Merge #1636bors[bot]2019-08-132-0/+69
|\ \ | |/ |/| | | | | | | | | | | 1636: fix block parse problem r=matklad a=bravomikekilo try to fix [issue-1598](https://github.com/rust-analyzer/rust-analyzer/issues/1598). Co-authored-by: bravomikekilo <[email protected]>
| * add inline testbravomikekilo2019-08-132-0/+69
| |
* | Move numeric names inside of `NameRef`Aleksey Kladov2019-08-093-7/+12
| |
* | Parse tuple struct field initializationEvgenii P2019-08-092-6/+28
| |
* | Merge #1661bors[bot]2019-08-084-0/+57
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1661: Parse function parameters attributes r=matklad a=eupn Fixes #1397. The [RFC-2565](https://github.com/rust-lang/rfcs/blob/master/text/2565-formal-function-parameter-attributes.md) specifies `#[attributes]` to function parameters: ```rust fn foo(#[attr] a, #[unused] b, #[must_use] ...) { // ... } ``` This PR adds those attributes into grammar and to the parser, extending corresponding inline tests. Co-authored-by: Evgenii P <[email protected]>
| * | Fix parser tests according to reviewEvgenii P2019-08-0816-485/+78
| | |
| * | Fix variadic arg inline testEvgenii P2019-08-072-24/+24
| | |
| * | Add function parameters attributesEvgenii P2019-08-0712-21/+485
| |/
* / assoc types boundsAleksey Kladov2019-08-072-0/+56
|/
* move syntax tests to unit testsAleksey Kladov2019-07-24298-0/+8747
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 08:12:38 +0000