| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-10-23 | Don't emit edits for postfix adjustment hints | Lukas Wirth | -23/+28 | |
| 2024-10-23 | Add text edit to implicit 'static hints | Lukas Wirth | -1/+2 | |
| 2024-10-23 | Add text edit to discriminant hints | Lukas Wirth | -5/+6 | |
| 2024-10-23 | Add text edit to binding mode hints | Lukas Wirth | -36/+38 | |
| 2024-10-23 | Add text edit to adjustment hints | Lukas Wirth | -21/+42 | |
| 2024-10-22 | Correctly resolve variables and labels from before macro definition in macro ↵ | Chayim Refael Friedman | -50/+287 | |
| expansion E.g.: ```rust let v; macro_rules! m { () => { v }; } ``` This was an existing bug, but it was less severe because unless the variable was shadowed it would be correctly resolved. With hygiene however, without this fix the variable is never resolved. | ||||
| 2024-10-22 | Implement semitransparent hygiene | Chayim Refael Friedman | -124/+394 | |
| Or macro_rules hygiene, or mixed site hygiene. In other words, hygiene for variables and labels but not items. The realization that made me implement this was that while "full" hygiene (aka. def site hygiene) is really hard for us to implement, and will likely involve intrusive changes and performance losses, since every `Name` will have to carry hygiene, mixed site hygiene is very local: it applies only to bodies, and we very well can save it in a side map with minor losses. This fixes one diagnostic in r-a that was about `izip!()` using hygiene (yay!) but it introduces a huge number of others, because of #18262. Up until now this issue wasn't a major problem because it only affected few cases, but with hygiene identifiers referred by macros like that are not resolved at all. The next commit will fix that. | ||||
| 2024-10-22 | Merge pull request #18254 from ChayimFriedman2/fix-mut | Lukas Wirth | -860/+1171 | |
| fix: Nail destructuring assignment once and for all | ||||
| 2024-10-22 | Add test for tuple struct destructuring assignment where the path comes from ↵ | Chayim Refael Friedman | -0/+34 | |
| a macro | ||||
| 2024-10-22 | docs: remove unnecessary prerequisites setup.md | David Kurilla | -9/+3 | |
| 2024-10-22 | Merge binding_mode inlay hints into one | Lukas Wirth | -11/+29 | |
| 2024-10-22 | Merge adjustment inlay hints into one | Lukas Wirth | -145/+83 | |
| 2024-10-22 | Merge closure capture inlay hints into one | Lukas Wirth | -90/+41 | |
| 2024-10-22 | Merge pull request #18372 from Kobzol/ci-merge-queue | Marco Ieni | -20/+17 | |
| Switch CI from bors to merge queues | ||||
| 2024-10-22 | Auto merge of #18370 - duncpro:goto-def-ranges, r=Veykril | bors | -8/+124 | |
| feat: resolve range patterns to their structs Closes #18367 | ||||
| 2024-10-22 | Auto merge of #18368 - Veykril:test-lsif_contains_generated_macros, r=lnicola | bors | -17/+199 | |
| tests: Add `lsif_contains_generated_constant` test Closes https://github.com/rust-lang/rust-analyzer/pull/18309 | ||||
| 2024-10-22 | Switch CI from bors to merge queues | Jakub Beránek | -20/+17 | |
| 2024-10-22 | Auto merge of #18349 - dqkqd:issue-18344, r=Veykril | bors | -1/+166 | |
| feat: render docs from aliased type when type has no docs Trying to close #18344 - [x] ~Find the docs by traversing upwards if the type itself has none but aliasing for another type that might have.~ - [x] Show docs from aliased type. - [x] Showing description that we are displaying documentation for different definition in hover box.  | ||||
| 2024-10-22 | Auto merge of #18371 - Veykril:veykril/push-kwttrusywysp, r=Veykril | bors | -25/+184 | |
| fix: Fix incorrect parsing of use bounds Fixes https://github.com/rust-lang/rust-analyzer/issues/18357 | ||||
| 2024-10-22 | fix: Fix incorrect parsing of use bounds | Lukas Wirth | -25/+184 | |
| Also lower them a bit more | ||||
| 2024-10-22 | feat: render docs from aliased type when docs are missing | Khanh Duong Quoc | -1/+166 | |
| 2024-10-22 | tidy | Duncan Proctor | -2/+1 | |
| 2024-10-22 | tidy | Duncan Proctor | -5/+5 | |
| 2024-10-22 | remove duplicate test | Duncan Proctor | -16/+0 | |
| 2024-10-22 | resolve range patterns to the their struct types | Duncan Proctor | -8/+141 | |
| 2024-10-22 | Fix new nightly lints | Lukas Wirth | -51/+81 | |
| 2024-10-22 | tests: Add `lsif_contains_generated_constant` test | Johann Hemmann | -17/+199 | |
| 2024-10-22 | Cleanup file structure proto handling | Lukas Wirth | -10/+3 | |
| 2024-10-22 | Fix status bar messagen not being marked markdown | Lukas Wirth | -1/+1 | |
| 2024-10-22 | Auto merge of #18362 - duncpro:goto-def-ranges, r=Veykril | bors | -17/+139 | |
| feat: goto definition on range operators Closes #18342 | ||||
| 2024-10-22 | tidy | Duncan Proctor | -15/+27 | |
| 2024-10-22 | Replace some LayoutError variants with the rustc_abi errors | Laurențiu Nicola | -24/+22 | |
| 2024-10-22 | Bump rustc crates | Laurențiu Nicola | -5/+5 | |
| 2024-10-22 | Merge from rust-lang/rust | Laurențiu Nicola | -5/+4 | |
| 2024-10-22 | Preparing for merge from rust-lang/rust | Laurențiu Nicola | -1/+1 | |
| 2024-10-22 | goto definition on RangeFrom, RangeFull, RangeTo, and RangeToInclusive links ↵ | Duncan Proctor | -36/+65 | |
| to respective struct | ||||
| 2024-10-21 | Move explicit range handling out of goto_definition, use OperatorClass instead | duncanproctor | -53/+70 | |
| 2024-10-21 | Auto merge of #18360 - roife:safe-kw-3, r=Veykril | bors | -54/+146 | |
| feat: better completions for extern blcoks This PR refactors `add_keywords` (making it much clearer!) and enhances completion for `extern` blocks. It is recommended to reviewing the changes in order of the commits: - The first commit (f3c4dde0a4917a2bac98605cc045eecfb4d69872) doesn’t change any logic but refactors parts of the `add_keywords` function and adds detailed comments. - The second commit (5dcc1ab649bf8a49cadf006d620871b12f093a2f) improves completion for `extern` kw and extern blocks. | ||||
| 2024-10-22 | minor: refactor completions in item_list | roife | -27/+24 | |
| 2024-10-21 | GotoDefinition on a Range or InclusiveRange operator will link to the struct ↵ | duncanproctor | -4/+68 | |
| definition | ||||
| 2024-10-21 | Auto merge of #18361 - Veykril:veykril/push-uzsokssoyznx, r=Veykril | bors | -41/+125 | |
| fix: Fix token downmapping failing for include! inputs Supercedes https://github.com/rust-lang/rust-analyzer/pull/18325 Fixes https://github.com/rust-lang/rust-analyzer/pull/18325 Fixes https://github.com/rust-lang/rust-analyzer/issues/18313 Fixes https://github.com/rust-lang/rust-analyzer/issues/18314 | ||||
| 2024-10-21 | fix: Fix token downmapping failing for include! inputs | Lukas Wirth | -41/+125 | |
| 2024-10-21 | feat: better completions for extern blcoks | roife | -18/+104 | |
| 2024-10-21 | refactor add_keywords in ide-completions for clarity | roife | -47/+56 | |
| 2024-10-21 | Auto merge of #18359 - Daanoz:support-initializeStopped, r=Veykril | bors | -1/+17 | |
| feat: support initializeStopped setting See #18356 Add option to start rust-analyzer in "stopped" state when the extension activates. | ||||
| 2024-10-21 | Auto merge of #18294 - Giga-Bowser:master, r=Veykril | bors | -2387/+4718 | |
| Add wrap/unwrap return type in Option I pretty much just copied over the code and tests for wrapping/unwrapping return types in `Result` and then did a bunch of find and replace changes. I handled unwrapping statements returning `None` by just replacing `None` with the unit type, but I'm open to suggestions for more intuitive behavior here. | ||||
| 2024-10-21 | Auto merge of #18337 - dqkqd:issue-18287, r=Veykril | bors | -4/+20 | |
| fix: private items are shown in completions for modules in fn body Close: #18287 | ||||
| 2024-10-21 | fix: private items are shown in completions for modules in fn body | Khanh Duong Quoc | -4/+20 | |
| 2024-10-21 | fix: FIx mbe bench tests being iteration order dependent | Lukas Wirth | -5/+8 | |
| 2024-10-21 | Update ide tests | Lukas Wirth | -178/+179 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |