| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2022-03-10 | Add support for new `where` clause location in associated types. | Dario Nieuwenhuis | -1/+6 | |
| A recent Rust nightly changed it: https://github.com/rust-lang/rust/issues/89122 This allows both the old and new location. | ||||
| 2022-02-14 | Fix style | bellau | -1/+1 | |
| 2022-02-13 | fix handle static async and static async move | bellau | -1/+1 | |
| 2022-02-12 | Fix style | bellau | -1/+1 | |
| 2022-02-12 | support static move too | bellau | -1/+1 | |
| 2022-02-12 | Fix styles | bellau | -1/+1 | |
| 2022-02-12 | Fix Immovable generator syntax (static ||) not recognized #11448 | bellau | -1/+1 | |
| 2021-12-12 | Switch parser to use tokens | Aleksey Kladov | -6/+6 | |
| 2021-11-10 | Handle pub tuple fields in tuple structs | Adam Bratschi-Kaye | -1/+1 | |
| The current implementation will throw a parser error for tuple structs that contain a pub tuple field. For example, ```rust struct Foo(pub (u32, u32)); ``` is valid Rust, but rust-analyzer will throw a parser error. This is because the parens after `pub` is treated as a visibility context. Allowing a tuple type to follow `pub` in the special case when we are defining fields in a tuple struct can fix the issue. | ||||
| 2021-10-03 | Add semicolons for consistency | Aramis Razzaghipour | -3/+3 | |
| `clippy::semicolon_if_nothing_returned` | ||||
| 2021-09-18 | internal: better naming | Aleksey Kladov | -5/+5 | |
| 2021-09-18 | internal: parser cleanup | Aleksey Kladov | -1/+1 | |
| 2021-09-18 | minor: better test placement | Aleksey Kladov | -7/+6 | |
| 2021-09-18 | internal: cleanup item parsing | Aleksey Kladov | -57/+39 | |
| 2021-09-18 | minor: parser cleanup | Aleksey Kladov | -19/+17 | |
| 2021-09-17 | minor: simplify | Aleksey Kladov | -3/+3 | |
| 2021-09-17 | internal: more local parsing tests for macros | Aleksey Kladov | -9/+4 | |
| 2021-09-17 | internal: more focused parsing tests | Aleksey Kladov | -48/+27 | |
| 2021-09-17 | internal: more local test for mod item | Aleksey Kladov | -22/+24 | |
| 2021-09-17 | internal: more local parsing tests | Aleksey Kladov | -2/+6 | |
| 2021-09-17 | internal: parser cleanups | Aleksey Kladov | -16/+15 | |
| 2021-08-30 | internal: improve style | Aleksey Kladov | -21/+19 | |
| Group related stuff together, use only on path for parsing extern blocks (they actually have modifiers). Perhaps we should get rid of items_without_modifiers altogether? Better to handle these kinds on diagnostics in validation layer... | ||||
| 2021-08-30 | fix: avoid panic when parsing extern block | Aleksey Kladov | -13/+13 | |
| closes #10083 | ||||
| 2021-05-22 | Add even more docs | Aleksey Kladov | -2/+0 | |
| 2021-02-15 | Specialization for async traits | Arnaud | -0/+28 | |
| 2021-01-15 | Wrap remaining self/super/crate in Name{Ref} | Lukas Wirth | -0/+2 | |
| 2021-01-10 | Replace SyntaxKind usage with T! macro where applicable | Lukas Wirth | -13/+13 | |
| 2020-12-24 | Fix macro_rules not accepting brackets or parentheses | Lukas Wirth | -2/+7 | |
| 2020-12-23 | Parse const effect block | Lukas Wirth | -2/+5 | |
| 2020-12-15 | Move to upstream `macro_rules!` model | Jonas Schievink | -13/+31 | |
| 2020-11-22 | Parse unsafe extern block | David Tolnay | -1/+9 | |
| 2020-11-06 | Kill RAW_ literals | Aleksey Kladov | -3/+1 | |
| Syntactically, they are indistinguishable from non-raw versions, so it doesn't make sense to separate then *at the syntax* level. | ||||
| 2020-08-27 | CONST LOOPS ARE HERE | Aleksey Kladov | -2/+2 | |
| 2020-08-13 | Better recovery in `use foo::;` | Aleksey Kladov | -2/+14 | |
| 2020-08-13 | Align parser names with grammar | Aleksey Kladov | -27/+27 | |
| 2020-08-12 | Rename ra_parser -> parser | Aleksey Kladov | -0/+432 | |
