aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_parser/src/grammar/expressions.rs
Commit message (Collapse)AuthorAgeFilesLines
* Move tests aroundGeoffry Song2019-10-061-6/+5
|
* Lower the precedence of the `as` operator.Geoffry Song2019-10-031-2/+12
| | | | | | | 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.
* Added test for check doc strings in crates.Alexander Andreev2019-09-301-0/+2
| | | | #1856
* Replace usages of bump_any with bumpkjeremy2019-09-191-10/+10
|
* cleanup dollar handling in expressionsAleksey Kladov2019-09-101-40/+9
|
* WIP: switch to fully decomposed tokens internallyAleksey Kladov2019-09-101-91/+107
|
* rename bump -> bump_anyAleksey Kladov2019-09-091-19/+19
|
* tiny simplificationAleksey Kladov2019-09-091-2/+2
|
* always wrap block into an expressionAleksey Kladov2019-09-021-0/+5
|
* rename struct -> record, pos -> tupleAleksey Kladov2019-08-231-7/+7
|
* Merge #1676bors[bot]2019-08-141-1/+1
|\ | | | | | | | | | | | | | | 1676: Fix for<'lifetime> for types specified by path r=matklad a=eupn Fixes #1467. Co-authored-by: Evgenii P <[email protected]>
| * Fix is_path_start to accept T![<], fix is_path_start usagesEvgenii P2019-08-131-1/+1
| |
* | Merge #1636bors[bot]2019-08-131-7/+12
|\ \ | |/ |/| | | | | | | | | | | 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-131-0/+6
| |
| * fix block parse problembravomikekilo2019-08-031-7/+6
| |
* | Move numeric names inside of `NameRef`Aleksey Kladov2019-08-091-6/+4
| |
* | Make name_ref to accept numeric names optionallyEvgenii P2019-08-091-3/+3
| |
* | Parse tuple struct field initializationEvgenii P2019-08-091-1/+2
|/
* add await to syntax, parser for await_exprUnreal Hoang2019-07-201-0/+12
|
* fixed #1384zjy2019-06-281-0/+11
|
* fix: never type with bindingcsmoe2019-06-071-1/+3
| | | | Change-Id: I14e1bc628b9d2dfdb1f40de3d3707f4e872767f2
* Fix clippy::if_same_then_elseAlan Du2019-06-041-0/+1
|
* apply T! macro where it is possibleSergey Parilin2019-05-151-78/+78
|
* Simplifykjeremy2019-04-261-6/+6
|
* Add expr, pat, ty and macro_stmtsEdwin Cheng2019-04-181-10/+34
|
* Add mbe stmt matcherEdwin Cheng2019-04-171-72/+82
|
* Fix bug and add expr , pat , ty matcherEdwin Cheng2019-04-141-9/+41
|
* Parse and infer tuple indicesrobojumper2019-04-061-1/+12
|
* Fix parsing <= in type_argsVille Penttinen2019-03-301-0/+1
|
* Replace `contract_child` to a less ad-hoc APIpcpthm2019-03-191-10/+10
|
* Error about attributes onpcpthm2019-03-191-12/+23
| | | | unallowed types of expression statement
* Allow attributes on top level expressionpcpthm2019-03-191-32/+51
| | | | | | A top level expression is either - a expression statement or - the last expression in a block
* Merge #991bors[bot]2019-03-181-2/+0
|\ | | | | | | | | | | | | | | | | | | | | | | 991: Use Marker argument for item parsers r=matklad a=pcpthm Before doing this for expressions, I found that the pattern (Marker argument) should be applied to the item parsers because visiblity and modifiers are parsed in a separate function. Fixed some parser bugs: - Fix pub_expr: `pub 42;` was allowed. - Fix incorrect parsing of crate::path: incorrectly parsed as `crate` as a visibility. Co-authored-by: pcpthm <[email protected]>
| * Use Marker argument for item parserspcpthm2019-03-181-2/+0
| | | | | | | | | | - Fix pub_expr - Fix incorrect parsing of crate::path
* | Merge #987bors[bot]2019-03-181-38/+32
|\| | | | | | | | | | | | | | | | | | | | | | | 987: Refactor maybe_item to use Marker argument r=pcpthm a=pcpthm As suggested at <https://github.com/rust-analyzer/rust-analyzer/pull/980#issuecomment-473659745>. For expression paring functions, changing signature - from `fn(&mut Parser) -> Option<CompletedMarker>` to `fn(&mut Parser, Marker) -> Result<CompletedMarker, Marker>` - from `fn(&mut Parser) -> CompletedMarker` to `fn(&mut Parser, Marker) -> CompletedMarker` is my plan. Co-authored-by: pcpthm <[email protected]>
| * Apply stylistic changes suggestedpcpthm2019-03-181-4/+4
| |
| * Refactor maybe_item to use Marker argumentpcpthm2019-03-171-39/+33
| |
* | Merge #983bors[bot]2019-03-171-0/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | 983: support remainder assignment operator r=matklad a=JeanMertz `%=` was returning errors for me, turns out it wasn't added as a valid assignment operation. I'm not sure what the best location would be to add a test for this. Please let me know and I'll add one. Co-authored-by: Jean Mertz <[email protected]>
| * support remainder assignment operatorJean Mertz2019-03-171-0/+1
| |
* | Merge #985bors[bot]2019-03-171-57/+56
|\ \ | | | | | | | | | | | | | | | | | | | | | 985: simplify parsing blocks a bit r=pcpthm a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | simplify parsing blocks a bitAleksey Kladov2019-03-171-57/+56
| |/
* / Allow attribute on struct literal fieldpcpthm2019-03-171-1/+6
|/
* extract block contents into a functionAleksey Kladov2019-03-041-2/+6
|
* move parser to a separate crateAleksey Kladov2019-02-211-0/+473