| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-08-18 | Auto-attach database in `Analysis` calls | Lukas Wirth | -2/+1 | |
| 2025-08-14 | feat: hint at unterminated strings in unknown prefix errors | Ralf Anton Beier | -1/+49 | |
| When encountering 'unknown literal prefix' errors, check for unbalanced quotes in recent code and suggest checking for unterminated string literals. | ||||
| 2025-08-13 | Merge Trait and TraitAlias handling | Deadbeef | -6/+4 | |
| 2025-08-10 | parser: fix parsing of trait bound polarity and for-binders | Nathaniel McCallum | -19/+73 | |
| The rustc AST allows both `for<>` binders and `?` polarity modifiers in trait bounds, but they are parsed in a specific order and validated for correctness: 1. `for<>` binder is parsed first. 2. Polarity modifiers (`?`, `!`) are parsed second. 3. The parser validates that binders and polarity modifiers do not conflict: ```rust if let Some(binder_span) = binder_span { match modifiers.polarity { BoundPolarity::Maybe(polarity_span) => { // Error: "for<...> binder not allowed with ? polarity" } } } ``` This implies: - `for<> ?Sized` → Valid syntax. Invalid semantics. - `?for<> Sized` → Invalid syntax. However, rust-analyzer incorrectly had special-case logic that allowed `?for<>` as valid syntax. This fix removes that incorrect special case, making rust-analyzer reject `?for<> Sized` as a syntax error, matching rustc behavior. This has caused confusion in other crates (such as syn) which rely on these files to implement correct syntax evaluation. | ||||
| 2025-07-31 | `cargo clippy --fix` | Lukas Wirth | -41/+38 | |
| 2025-07-22 | Parse `for<'a> [const]` | Chayim Refael Friedman | -238/+360 | |
| And also refactor parsing of HRTB. | ||||
| 2025-07-15 | Format and bump rustc crates | Laurențiu Nicola | -2/+2 | |
| 2025-07-15 | Merge from rust-lang/rust | Laurențiu Nicola | -4/+6 | |
| 2025-07-10 | Merge pull request #20210 from ChayimFriedman2/naked-asm-safe | Shoyu Vanilla (Flint) | -9/+106 | |
| fix: Inline asm fixes | ||||
| 2025-07-09 | feat(lexer): Allow including frontmatter with 'tokenize' | Ed Page | -4/+6 | |
| 2025-07-09 | Make `global_asm!()` work | Chayim Refael Friedman | -12/+37 | |
| Because apparently, we were not accepting inline asm in item position, completely breaking it. | ||||
| 2025-07-09 | Differentiate between `asm!()`, `global_asm!()` and `naked_asm!()`, and make ↵ | Chayim Refael Friedman | -7/+79 | |
| only `asm!()` unsafe | ||||
| 2025-07-06 | Always bump in the parser in `err_and_bump()` | Chayim Refael Friedman | -5/+9 | |
| Even when at curly braces, otherwise the parser can get stuck. This has happened in the past in #18625, but it was just worked around instead of handling the root of the problem. Now this happened again in #20171. IMO we can't let `err_and_bump()` not bump, that's too confusing and invites errors. We can (as I did) workaround the worse recovery instead. | ||||
| 2025-06-26 | Parse new const trait syntax | Lukas Wirth | -3/+9 | |
| 2025-06-24 | Merge pull request #20012 from lnicola/bump-literal-escaper | Lukas Wirth | -71/+60 | |
| Update to literal-escaper 0.0.4 | ||||
| 2025-06-23 | Don't run doctests | Chayim Refael Friedman | -0/+1 | |
| 2025-06-16 | update to literal-escaper 0.0.4 for better API without `unreachable` and ↵ | Marijn Schouten | -71/+60 | |
| faster string parsing | ||||
| 2025-06-05 | Better parser recovery for macro calls in type bound position | Lukas Wirth | -10/+134 | |
| 2025-06-04 | Give path segment type anchors their own grammar rule | Lukas Wirth | -129/+145 | |
| 2025-05-30 | Update expected test output | Arthur Baars | -21/+60 | |
| 2025-05-30 | Run 'cargo codegen' to update tests | Arthur Baars | -0/+5 | |
| 2025-05-30 | Add test for closure_binder | Arthur Baars | -0/+2 | |
| Co-authored-by: Lukas Wirth <me@lukaswirth.dev> | ||||
| 2025-05-30 | Produce ClosureBinder node in atom.rs | Arthur Baars | -0/+2 | |
| 2025-05-20 | Bump rustc crates | Laurențiu Nicola | -1/+4 | |
| 2025-05-20 | Merge from rust-lang/rust | Laurențiu Nicola | -1/+12 | |
| 2025-05-15 | Improve asm support | Chayim Refael Friedman | -2/+48 | |
| Including: - Infer `label {}` and `const` operands. - Correctly handle unsafe check inside `label {}`. - Fix an embarrassing parser typo that cause labels to never be part of the AST | ||||
| 2025-05-06 | Rollup merge of #140035 - fee1-dead-contrib:push-oszwkkvmpkks, ↵ | Stuart Cook | -1/+12 | |
| r=jieyouxu,wesleywiser Implement RFC 3503: frontmatters Tracking issue: #136889 Supercedes #137193. This implements [RFC 3503](https://github.com/rust-lang/rfcs/blob/master/text/3503-frontmatter.md). This might break rust-analyzer. Will look into how to fix that. Suggestions welcome for how to improve diagnostics. | ||||
| 2025-05-05 | Implement RFC 3503: frontmatters | Deadbeef | -1/+12 | |
| Supercedes #137193 | ||||
| 2025-04-30 | fix: Improve parser recovery a bit | Lukas Wirth | -14/+84 | |
| 2025-04-28 | Format code | Laurențiu Nicola | -1/+3 | |
| 2025-04-28 | Merge from rust-lang/rust | Laurențiu Nicola | -5/+6 | |
| 2025-04-25 | Preallocate `parser::Input` | Chayim Refael Friedman | -2/+9 | |
| 2025-04-22 | Merge pull request #19657 from ChayimFriedman2/better-offset-of | Lukas Wirth | -0/+61 | |
| feat: Better support `offset_of!()` | ||||
| 2025-04-21 | Merge pull request #19643 from ChayimFriedman2/generic-const-items | Lukas Wirth | -0/+296 | |
| feat: Parse generic consts | ||||
| 2025-04-21 | feat: parse `super let` | Lukas Wirth | -3/+27 | |
| 2025-04-21 | Allow wrapping `builtin#offset_of` fields argument in parentheses | Chayim Refael Friedman | -0/+61 | |
| This is necessary to correctly handle nested fields (`foo.bar`), see the comments in the code for explanation. | ||||
| 2025-04-21 | Parse generic consts | Chayim Refael Friedman | -0/+296 | |
| A lang team experiment, https://github.com/rust-lang/rust/issues/113521. | ||||
| 2025-04-05 | Clean up `rustc-literal-escaper` usage in rust-analyzer | Guillaume Gomez | -1/+1 | |
| 2025-04-04 | Update `rustc-literal-escaper` version to `0.0.2` | Guillaume Gomez | -1/+1 | |
| 2025-04-04 | Remove usage of `rustc_lexer::unescape` in rust-analyzer | Guillaume Gomez | -5/+6 | |
| 2025-03-25 | feat: parse `unsafe` record fields | Lukas Wirth | -2/+17 | |
| 2025-03-23 | chore: Bump dependencies | Lukas Wirth | -1/+1 | |
| 2025-03-21 | fix: Fix incorrect expansion of builtin `PartialOrd` derive | Lukas Wirth | -0/+1 | |
| 2025-03-21 | refactor: Reduce codegen burden for `SyntaxNode` and `SyntaxToken` | Lukas Wirth | -1/+1 | |
| 2025-03-21 | refactor: Reduce codegen burden for `SyntaxKind` | Lukas Wirth | -32/+29 | |
| 2025-03-17 | chore: Bump `Edition::CURRENT` to 2024 | Lukas Wirth | -5/+13 | |
| 2025-03-15 | cargo fmt | BenjaminBrienen | -7/+7 | |
| 2025-03-08 | fix(hir): `VariantDef` is `impl HasSource` | Prajwal S N | -0/+2 | |
| A new syntax node `ast::VariantDef` has been introduced to map between the HIR node and the AST. The files have been updated with `cargo test -p xtask`. Signed-off-by: Prajwal S N <prajwalnadig21@gmail.com> | ||||
| 2025-03-01 | Cleanup string handling in syntax highlighting | Lukas Wirth | -18/+1 | |
| 2025-02-27 | fix doc tests | BenjaminBrienen | -4/+5 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |