| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Merge #1685 | bors[bot] | 2019-08-15 | 1 | -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 position | bravomikekilo | 2019-08-14 | 1 | -10/+6 |
| | | | |||||
| | * | fix error of RangeFrom in for-loop | bravomikekilo | 2019-08-14 | 1 | -1/+17 |
| | | | |||||
| * | | Fix is_path_start to accept T![<], fix is_path_start usages | Evgenii P | 2019-08-13 | 1 | -1/+1 |
| |/ | |||||
| * | fix: parse box syntax inside parentheses | csmoe | 2019-07-22 | 1 | -0/+3 |
| | | |||||
| * | Remove parse error on array initializer attributes | Ryan Cumming | 2019-06-30 | 1 | -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 members | Ryan Cumming | 2019-06-30 | 1 | -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_pattern | csmoe | 2019-06-19 | 1 | -0/+15 |
| | | | | | Change-Id: I45a856d74fb616d3bce33050f9e69d327186bd59 | ||||
| * | [#1083] Try block syntax: fix tests | Andrey Tkachenko | 2019-06-06 | 1 | -7/+7 |
| | | |||||
| * | [#1083] Try block syntax | Andrey Tkachenko | 2019-06-06 | 1 | -1/+17 |
| | | |||||
| * | apply T! macro where it is possible | Sergey Parilin | 2019-05-15 | 1 | -72/+72 |
| | | |||||
| * | Merge #1082 | bors[bot] | 2019-04-01 | 1 | -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 position | Andrey Tkachenko | 2019-04-01 | 1 | -0/+1 |
| | | | |||||
| * | | Async closure syntax | robojumper | 2019-03-31 | 1 | -2/+12 |
| |/ | |||||
| * | recognize async move | memoryruins | 2019-03-28 | 1 | -2/+2 |
| | | |||||
| * | Allow attributes on top level expression | pcpthm | 2019-03-19 | 1 | -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 arm | pcpthm | 2019-03-17 | 1 | -15/+15 |
| | | |||||
| * | Add async keyword | Caio | 2019-03-09 | 1 | -0/+5 |
| | | |||||
| * | Introduce pattern_list to parse pipe separated patterns | Ville Penttinen | 2019-03-05 | 1 | -10/+2 |
| | | | | | | 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. | ||||
| * | Add support for parsing multiple if and while-let patterns | Ville Penttinen | 2019-03-04 | 1 | -0/+10 |
| | | |||||
| * | move parser to a separate crate | Aleksey Kladov | 2019-02-21 | 1 | -0/+475 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |