aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_parser/src/grammar/expressions
Commit message (Collapse)AuthorAgeFilesLines
* Rename ra_parser -> parserAleksey Kladov2020-08-121-611/+0
|
* Rename LambdaExpr -> ClosureExprAleksey Kladov2020-07-311-1/+1
|
* Fix parsing of blocks without `{`Aleksey Kladov2020-05-021-18/+23
|
* Cleanup inline testsAleksey Kladov2020-05-021-2/+4
|
* Introduce EffectExprAleksey Kladov2020-05-021-11/+18
|
* Revert "Merge #4233"Aleksey Kladov2020-05-021-3/+3
| | | | | This reverts commit a5f2b16366f027ad60c58266a66eb7fbdcbda9f9, reversing changes made to c96b2180c1c4206a0a98c280b4d30897eb116336.
* Remove dead code, which elaborately pretends to be aliveAleksey Kladov2020-04-301-3/+3
|
* Special-case try macro to better support 2015 editionAleksey Kladov2020-04-301-0/+16
|
* 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
* Better fix for stuck parser?Florian Diebold2020-03-161-3/+3
|
* Get tests workingFlorian Diebold2020-03-161-2/+2
|
* Run cargo +nightly fix --clippy -Z unstable-optionsKirill Bulatov2020-02-181-4/+2
|
* Add or- and parenthesized-patternsMatthew Jasper2020-02-091-2/+2
|
* Rework value parameter parsingToby Dimmick2020-02-061-1/+1
| | | | | | | - `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
* Extract expr_with_attrsAleksey Kladov2020-01-171-13/+2
|
* Minimize testAleksey Kladov2020-01-161-13/+3
|
* Simplify array parsingAleksey Kladov2020-01-161-26/+31
|
* Fix array element attribute positionEdwin Cheng2020-01-161-6/+8
|
* Touch up TokenSet a bitAleksey Kladov2019-12-191-1/+1
|
* Fix parsing of interpolated expressionsAleksey Kladov2019-12-191-0/+1
|
* Improve recovery for incomplete lambdasAleksey Kladov2019-12-171-1/+6
|
* Simplify parsingAleksey Kladov2019-11-141-17/+17
|
* fix parsing of for loops inside expressionsAleksey Kladov2019-10-281-1/+2
| | | | closes #2051
* Fix parsing of block expressions in "forbid_structs" contexts.Geoffry Song2019-10-031-5/+5
| | | | | | 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).
* Added test for check doc strings in crates.Alexander Andreev2019-09-301-0/+2
| | | | #1856
* Support loop as argumentkjeremy2019-09-201-0/+1
|
* Replace usages of bump_any with bumpkjeremy2019-09-191-16/+16
|
* cleanup dollar handling in expressionsAleksey Kladov2019-09-101-0/+25
|
* rename bump -> bump_anyAleksey Kladov2019-09-091-18/+18
|
* always wrap block into an expressionAleksey Kladov2019-09-021-2/+2
|
* Centralize `box` pattern tests in `patterns.rs`Dylan MacKenzie2019-08-241-2/+0
|
* Add test for nested box patternDylan MacKenzie2019-08-221-0/+2
|
* Merge #1685bors[bot]2019-08-151-1/+13
|\ | | | | | | | | | | | | | | 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-141-10/+6
| |
| * fix error of RangeFrom in for-loopbravomikekilo2019-08-141-1/+17
| |
* | Fix is_path_start to accept T![<], fix is_path_start usagesEvgenii P2019-08-131-1/+1
|/
* fix: parse box syntax inside parenthesescsmoe2019-07-221-0/+3
|
* Remove parse error on array initializer attributesRyan Cumming2019-06-301-11/+0
| | | | | This is actually allowed by the `rustc` parser but most attributes will fail later due to attributes on expressions being experimental.
* Support attributes on array membersRyan Cumming2019-06-301-0/+28
| | | | | | | | | | | | Array members are allow to have attributes such as `#[cfg]`. This is a bit tricky as we don't know if the first expression is an initializer or a member until we encounter a `;`. This reuses a trick from `stmt` where we remember if we saw an attribute and then raise an error if the first expression ends up being an initializer. This isn't perfect as the error isn't correctly located on the attribute or initializer; it ends up immediately after the `;`.
* fix: box_patterncsmoe2019-06-191-0/+15
| | | | Change-Id: I45a856d74fb616d3bce33050f9e69d327186bd59
* [#1083] Try block syntax: fix testsAndrey Tkachenko2019-06-061-7/+7
|
* [#1083] Try block syntaxAndrey Tkachenko2019-06-061-1/+17
|
* apply T! macro where it is possibleSergey Parilin2019-05-151-72/+72
|
* Merge #1082bors[bot]2019-04-011-0/+1
|\ | | | | | | | | | | | | | | 1082: Async block in argument position r=matklad a=andreytkachenko Fixes case when async block appears in argument position Co-authored-by: Andrey Tkachenko <[email protected]>
| * Async block in argument positionAndrey Tkachenko2019-04-011-0/+1
| |
* | Async closure syntaxrobojumper2019-03-311-2/+12
|/
* recognize async movememoryruins2019-03-281-2/+2
|
* Allow attributes on top level expressionpcpthm2019-03-191-2/+2
| | | | | | A top level expression is either - a expression statement or - the last expression in a block
* Fix parse tree of attribute on match armpcpthm2019-03-171-15/+15
|
* Add async keywordCaio2019-03-091-0/+5
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 03:29:39 +0000