about summary refs log tree commit diff
path: root/src/tools/rust-analyzer
AgeCommit message (Collapse)AuthorLines
2025-08-10internal: Make flycheck generationalShoyu Vanilla-38/+148
2025-08-10Merge pull request #20418 from A4-Tacks/fix-extract-expr-from-fmtstr-on-writeChayim Refael Friedman-6/+40
Fix extract_expressions_from_format_string on write!
2025-08-10Fix extract_expressions_from_format_string on write!A4-Tacks-6/+40
**Input**: ```rust fn main() { write!(f, "{2+3}$0") } ``` **Old output**: ```rust fn main() { write!("{}"$0, 2+3) } ``` **This PR output**: ```rust fn main() { write!(f, "{}"$0, 2+3) } ```
2025-08-10parser: fix parsing of trait bound polarity and for-bindersNathaniel 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-08-10Merge pull request #20409 from A4-Tacks/minicore-writeChayim Refael Friedman-0/+21
Add write! and writeln! to minicore
2025-08-09Implement next trait solverjackh726-1309/+19140
2025-08-09remove `P`Deadbeef-4/+4
2025-08-09fix: generate function by indet tokenHmikihiro-1/+29
2025-08-08remove duplicate field in DebugBenjaminBrienen-1/+0
2025-08-09Add write! and writeln! to minicoreA4-Tacks-0/+21
2025-08-07Merge pull request #20400 from rust-lang/veykril/push-ksxzmxqymstoLukas Wirth-6/+7
Disable error log for position clamping, its too noisy due to ease of triggering
2025-08-07Disable error log for position clamping, its too noisy due to ease of triggeringLukas Wirth-6/+7
2025-08-07Enable warning logs by defaultLukas Wirth-2/+2
2025-08-07Rollup merge of #144682 - nxsaken:strict_overflow_ops, r=Mark-SimulacrumStuart Cook-14/+0
Stabilize `strict_overflow_ops` Closes rust-lang/rust#118260
2025-08-07Merge pull request #20394 from ↵Shoyu Vanilla (Flint)-3/+3
rust-lang/dependabot/npm_and_yarn/editors/code/tmp-0.2.4 Bump tmp from 0.2.3 to 0.2.4 in /editors/code
2025-08-07In extract_module.rs, generate ast::Module instead of StringHmikihiro-66/+126
2025-08-06Bump tmp from 0.2.3 to 0.2.4 in /editors/codedependabot[bot]-3/+3
Bumps [tmp](https://github.com/raszi/node-tmp) from 0.2.3 to 0.2.4. - [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md) - [Commits](https://github.com/raszi/node-tmp/compare/v0.2.3...v0.2.4) --- updated-dependencies: - dependency-name: tmp dependency-version: 0.2.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2025-08-06Merge pull request #20393 from rust-lang/veykril/push-urpzrkwpkmxwLukas Wirth-29/+29
Fix non-lsp compliant `Response` definition
2025-08-06Fix non-lsp compliant `Response` definitionLukas Wirth-29/+29
2025-08-06Merge pull request #20392 from rust-lang/veykril/push-pxplxplxvvyyLukas Wirth-4/+8
Report the incorrect payload when failing to deserialize lsp messages
2025-08-06Report the incorrect payload when failing to deserialize lsp messagesLukas Wirth-4/+8
2025-08-06Merge pull request #20354 from A4-Tacks/clean-lit-stmt-remove-dbgChayim Refael Friedman-0/+50
Add remove literal dbg stmt for remove_dbg
2025-08-06Add remove simple dbg stmt for remove_dbgA4-Tacks-0/+50
Remove only contain literals dbg statement ```rust fn foo() { let n = 2; $0dbg!(3); dbg!(2.6); dbg!(1, 2.5); dbg!('x'); dbg!(&n); dbg!(n); // needless comment dbg!("foo");$0 } ``` -> ```rust fn foo() { // needless comment } ``` Old: ```rust fn foo() { 3; 2.6; (1, 2.5); 'x'; &n; n; // needless comment "foo"; } ```
2025-08-06Merge pull request #20387 from ChayimFriedman2/rename-macroShoyu Vanilla (Flint)-63/+81
fix: Do not remove the original token when descending into derives
2025-08-05Merge pull request #20384 from vxpm/fix-external-docsChayim Refael Friedman-1/+26
fix external docs for exported macros
2025-08-05fix external docs for exported macrosvinícius x-1/+26
add test
2025-08-05Merge pull request #20381 from A4-Tacks/fix-assign-sugChayim Refael Friedman-0/+82
Add assignment type analysis for ide-completion
2025-08-05Change prev whitespace to prev triviaA4-Tacks-3/+3
2025-08-05Merge pull request #20385 from Hmikihiro/migrate_expand_glob_importShoyu Vanilla (Flint)-5/+4
Migrate `expand_glob_import` assist to use `SyntaxEditor`
2025-08-05Merge pull request #20383 from ↵Shoyu Vanilla (Flint)-17/+19
Hmikihiro/remove_ted_from_replace_named_generic_with_impl remove `ted` from replace_named_generic_with_impl.rs
2025-08-05Merge pull request #20380 from Hmikihiro/add_attr_argShoyu Vanilla (Flint)-116/+185
remove `add_attr()` from edit_in_place.rs because it use `ted`.
2025-08-05Merge pull request #20389 from Veykril/push-ssyssvnrywvyLukas Wirth-7/+3
Slim down compile time artifact progress reports
2025-08-05Slim down compile time artifact progress reportsLukas Wirth-7/+3
2025-08-05Do not remove the original token when descending into derivesChayim Refael Friedman-11/+9
This caused rename to remove both, because it couldn't rename the derive-expanded one. I spent some time trying to create a test for this, before giving up. But I checked manually that this works.
2025-08-05Allow renaming when there are multiple definitions (due to macros) even when ↵Chayim Refael Friedman-52/+72
some cannot rename
2025-08-05Migrate `expand_glob_import` assist to use `SyntaxEditor`Hmikihiro-5/+4
2025-08-05remove `ted` from replace_named_generic_with_impl.rsHmikihiro-17/+19
2025-08-04Merge pull request #20378 from skewb1k/chore/folding_ranges-permsLaurențiu Nicola-0/+0
chore: fix crates/ide/src/folding_ranges.rs file perms
2025-08-04Merge pull request #20382 from ChayimFriedman2/goto-def-from-macroShoyu Vanilla (Flint)-4/+30
fix: Correctly goto `From` impl when on `into()` even when the call is inside a macro
2025-08-04Add if..else completions in LetStmt and ArgListA4-Tacks-1/+127
Example === ```rust let x = $0; ``` Old completions: ```rust let x = if $1 { $0 }; ``` This PR current completions: ```rust let x = if $1 { $2 } else { $0 }; ```
2025-08-04Correctly goto `From` impl when on `into()` even when the call is inside a macroChayim Refael Friedman-4/+30
Descend into macros first.
2025-08-04remvoe add_attr edit_in_place.rs because it use ted.Hmikihiro-116/+185
2025-08-04fix(hover): unify horizontal rule formatting to `---`skewb1k-42/+42
Replaces all `___` with `---` in hover documentation markups. Both styles are valid per the GitHub Flavored Markdown spec, but `---` is less ambiguous and already more widely used in rust-analyzer
2025-08-04chore: fix crates/ide/src/folding_ranges.rs file permsskewb1k-0/+0
755 -> 644
2025-08-04Remove strict_overflow_ops lintNurzhan Sakén-14/+0
2025-08-04Add assignment type analysis for ide-completionA4-Tacks-0/+82
2025-08-03Remove unused functions from edit_in_placeHmikihiro-161/+2
2025-08-03Merge pull request #20371 from Hmikihiro/migrate_generate_trait_from_implLukas Wirth-34/+35
Migrate `generate_trait_from_impl` assist to use `SyntaxEditor`
2025-08-03Migrate `generate_trait_from_impl` assist to use `SyntaxEditor`Hmikihiro-34/+35
2025-08-03Merge pull request #20368 from Hmikihiro/migrate_delegate_methodsLukas Wirth-36/+41
Migrate `generate_delegate_methods` assist to use `SyntaxEditor`
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 14:14:08 +0000