aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_parser/src/grammar/patterns.rs
Commit message (Collapse)AuthorAgeFilesLines
* Rename DotDotPat -> RestPatAleksey Kladov2020-07-311-2/+2
|
* Rename BindPat -> IdentPatAleksey Kladov2020-07-311-1/+1
|
* Rename PalceholderPat -> WildcardPatAleksey Kladov2020-07-311-1/+1
|
* Allign RecordPat with RecordExprAleksey Kladov2020-07-311-2/+2
|
* Correctly parse <_> paths in patternsAleksey Kladov2020-06-091-2/+4
| | | | closes #3659
* Minor, use `T!`Aleksey Kladov2020-06-091-1/+1
|
* Align grammar for record patterns and literalsAleksey Kladov2020-04-111-27/+23
| | | | | | The grammar now looks like this [name_ref :] pat
* Macro patterns are not confused with expressions.Aleksey Kladov2020-04-031-2/+2
| | | | | | | | | | | 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-031-12/+11
|
* Address review commentsMatthew Jasper2020-02-101-7/+8
|
* Add or- and parenthesized-patternsMatthew Jasper2020-02-091-10/+56
|
* Fix parser for macro call in pattern positionEdwin Cheng2019-12-201-1/+1
|
* Added test for check doc strings in crates.Alexander Andreev2019-09-301-0/+2
| | | | #1856
* Simplify match armkjeremy2019-09-201-2/+1
|
* Apply suggestionkjeremy2019-09-201-3/+2
|
* Add indexing to record_field_patkjeremy2019-09-201-2/+13
|
* Replace usages of bump_any with bumpkjeremy2019-09-191-7/+7
|
* Parse `..` as a proper patternDylan MacKenzie2019-09-151-10/+42
|
* WIP: switch to fully decomposed tokens internallyAleksey Kladov2019-09-101-14/+19
|
* rename bump -> bump_anyAleksey Kladov2019-09-091-11/+11
|
* cleanupAleksey Kladov2019-09-021-1/+1
|
* Handle `Struct { box i }` syntaxDylan MacKenzie2019-08-241-0/+3
| | | | | | Named structs can have `box` patterns that will bind to their fields. This is similar to the behavior of the `ref` and `mut` fields, but is at least a little bit surprising.
* Centralize `box` pattern tests in `patterns.rs`Dylan MacKenzie2019-08-241-5/+0
|
* Parse `BoxPat`Dylan MacKenzie2019-08-241-19/+32
|
* rename struct -> record, pos -> tupleAleksey Kladov2019-08-231-8/+8
|
* Add BOX_KW to PATTERN_FIRSTDylan MacKenzie2019-08-221-1/+1
|
* Fix is_path_start to accept T![<], fix is_path_start usagesEvgenii P2019-08-131-2/+2
|
* fix: box_patterncsmoe2019-06-191-0/+3
| | | | Change-Id: I45a856d74fb616d3bce33050f9e69d327186bd59
* apply T! macro where it is possibleSergey Parilin2019-05-151-39/+39
|
* Add macro pat parsingEdwin Cheng2019-04-301-1/+10
|
* Fix bug and add expr , pat , ty matcherEdwin Cheng2019-04-141-1/+1
|
* Allow MINUS at the start of a pattern.Michael Chesser2019-03-141-1/+1
|
* Introduce pattern_list to parse pipe separated patternsVille Penttinen2019-03-051-0/+16
| | | | | pattern_list comes in two variants, one uses the default PAT_RECOVERY_SET as the recovery set, while other allows the user to provide a recovery set.
* move parser to a separate crateAleksey Kladov2019-02-211-0/+248
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 07:39:16 +0000