aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* allow modifications of vars from outer scope inside extracted functionVladyslav Katasonov2021-02-032-46/+337
| | | | | It currently allows only directly setting variable. No `&mut` references or methods.
* allow local variables to be used after extracted bodyVladyslav Katasonov2021-02-031-41/+183
| | | | | when variable is defined inside extracted body export this variable to original scope via return value(s)
* change TODO to FIXMEVladyslav Katasonov2021-02-031-2/+2
|
* disable test for downgrading mutability on extractVladyslav Katasonov2021-02-031-0/+3
|
* convert IdentPat to Pat via IntoVladyslav Katasonov2021-02-031-5/+5
| | | | before child getter was used
* support extracting methods; no mut loweringVladyslav Katasonov2021-02-031-37/+191
| | | | | currently mut refernce will *not* be downgraded to shared if it is sufficient(see relevant test for example)
* initial version of extract function assistVladyslav Katasonov2021-02-033-0/+848
| | | | | | | | there are a few currently limitations: * no modifications of function body * does not handle mutability and references * no method support * may produce incorrect results
* Merge #7525bors[bot]2021-02-022-2/+7
|\ | | | | | | | | | | | | | | | | | | | | 7525: Fix resolution of `crate` paths from within blocks r=jonas-schievink a=jonas-schievink They resolve to the crate root, not the DefMap's root module (which can be a block) bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * Fix resolution of `crate` paths from within blocksJonas Schievink2021-02-022-2/+7
|/ | | | | They resolve to the crate root, not the DefMap's root module (which can be a block)
* Merge #7523bors[bot]2021-02-024-16/+16
|\ | | | | | | | | | | | | | | 7523: Bump chalk and rustc_lexer r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * Bump rustc_lexerLaurențiu Nicola2021-02-022-3/+3
| |
| * Bump chalkLaurențiu Nicola2021-02-023-13/+13
|/
* Merge #7522bors[bot]2021-02-023-7/+6
|\ | | | | | | | | | | | | | | | | | | | | 7522: Use non-deprecated memmap2 crate r=kjeremy a=kjeremy `cargo audit` complains that `memmap` is unmaintained so switch to RazrFalcon's maintained version. Removes yet another edge on winapi Co-authored-by: kjeremy <[email protected]>
| * Use non-deprecated memmap2 cratekjeremy2021-02-023-7/+6
|/ | | | | | | `cargo audit` complains that `memmap` is unmaintained so switch to RazrFalcon's maintained version. Removes yet another edge on winapi
* Merge #7521bors[bot]2021-02-021-4/+4
|\ | | | | | | | | | | | | | | 7521: cargo update r=kjeremy a=kjeremy Pulls in soundness fix from rowan. Co-authored-by: kjeremy <[email protected]>
| * cargo updatekjeremy2021-02-021-4/+4
| |
* | Merge #7520bors[bot]2021-02-021-1/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7520: Show alias underlying type r=lnicola a=lumenian Closes #7511 Display underlying type in the tooltip: ```rust pub type SomeAlias = f64 ``` instead of: ```rust pub type SomeAlias ``` Co-authored-by: lumenian <[email protected]>
| * Show alias underlying typelumenian2021-02-021-1/+5
|/
* Merge #7519bors[bot]2021-02-021-0/+14
|\ | | | | | | | | | | | | | | 7519: add useless types to the styleguide r=matklad a=matklad bors r+ Co-authored-by: Aleksey Kladov <[email protected]>
| * add useless types to the styleguideAleksey Kladov2021-02-021-0/+14
|/
* Merge #7518bors[bot]2021-02-023-2/+20
|\ | | | | | | | | | | | | | | | | | | 7518: Use the right `DefMap` when looking up modules r=jonas-schievink a=jonas-schievink Fixes the bugs encountered in https://github.com/rust-analyzer/rust-analyzer/pull/7506#issuecomment-771417467 bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * Use the right `DefMap` when looking up modulesJonas Schievink2021-02-023-2/+20
|/
* Merge #7516bors[bot]2021-02-0210-161/+96
|\ | | | | | | | | | | | | | | | | | | 7516: Revert "Use block_def_map in body lowering" r=jonas-schievink a=jonas-schievink Reverts rust-analyzer/rust-analyzer#7506 bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * Revert "Use block_def_map in body lowering"Jonas Schievink2021-02-0210-161/+96
|/
* Merge #7514bors[bot]2021-02-011-14/+16
|\ | | | | | | | | | | | | | | | | | | 7514: Only allow one proc-macro process r=edwin0cheng a=edwin0cheng cc @lnicola bors r+ Co-authored-by: Edwin Cheng <[email protected]>
| * Only allow one proc-macro processEdwin Cheng2021-02-011-14/+16
|/
* Merge #7512bors[bot]2021-02-013-8/+5
|\ | | | | | | | | | | | | | | 7512: Reap proc macro server instances r=lnicola a=lnicola Fixes #7510, but not the root cause. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Reap proc macro server instancesLaurențiu Nicola2021-02-013-8/+5
|/
* Merge #7509bors[bot]2021-02-011-1/+34
|\ | | | | | | | | | | | | | | 7509: Improve nvim-lsp setup instructions r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * Improve nvim-lsp setup instructionsLaurențiu Nicola2021-02-011-1/+34
|/
* Merge #7508bors[bot]2021-02-012-5/+48
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7508: Don't filter code suggestions on Applicability r=lnicola a=CryZe I've noticed that there are various suggestions that rust-analyzer seems to filter out, even if they make sense. Here's an example of where it seems like there should be a suggestion, but there isn't: ![https://i.imgur.com/wsjM6iz.png](https://i.imgur.com/wsjM6iz.png) It turns out that this specific suggestion is not considered `MachineApplicable`, which are the only suggestions that rust-analyzer accepts. However if you read the documentation for `MachineApplicable`, [Source](https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L27-L29) ```rust /// The suggestion is definitely what the user intended. This suggestion should be /// automatically applied. MachineApplicable, ``` then you realize that these are specifically only those suggestions that rust-analyzer could even automatically apply (in some distant future, behind some setting or command or so). Other suggestions that may have some semantic impact do not use `MachineApplicable`. So all other suggestions are still intended to be suggested to the user, just not automatically applied without the user being consulted. [Source](https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L22-L24) ```rust /// All suggestions are marked with an `Applicability`. Tools use the applicability of a suggestion /// to determine whether it should be automatically applied or if the user should be consulted /// before applying the suggestion. ``` So with that in mind, rust-analyzer should almost definitely not filter out `MaybeIncorrect` (which honestly is named horribly, it just means that it's a semantic change, not just a syntactical one). Then there's `HasPlaceholders` which basically is just another semantic one, but with placeholders. The user will have to make some adjustments, but the suggestion still is perfectly valid. rust-analyzer could probably detect those placeholders and put proper "tab through" markers there for the IDE, but that's not necessary for now. Then the last one is `Unspecified` which is so unknown that I don't even know how to judge it, meaning that the suggestion should probably also just be suggested to the user and then they can decide. So with all that in mind, I'm proposing to get rid of the check for Applicability entirely. Co-authored-by: Christopher Serr <[email protected]>
| * Update Test DataChristopher Serr2021-02-011-1/+46
| |
| * Don't filter code suggestions on ApplicabilityChristopher Serr2021-02-011-4/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've noticed that there are various suggestions that rust-analyzer seems to filter out, even if they make sense. Here's an example of where it seems like there should be a suggestion, but there isn't: ![https://i.imgur.com/wsjM6iz.png](https://i.imgur.com/wsjM6iz.png) It turns out that this specific suggestion is not considered `MachineApplicable`, which are the only suggestions that rust-analyzer accepts. However if you read the documentation for `MachineApplicable`, https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L27-L29 then you realize that these are specifically only those suggestions that rust-analyzer could even automatically apply (in some distant future, behind some setting or so). Other suggestions that may have some semantic impact do not use `MachineApplicable`. So all other suggestions are still intended to be suggested to the user, just not automatically applied without the user being consulted. https://github.com/rust-lang/rust/blob/b3897e3d1302391ed02efbac1dce8073646b8173/compiler/rustc_lint_defs/src/lib.rs#L22-L24 So with that in mind, rust-analyzer should almost definitely not filter out `MaybeIncorrect` (which honestly is named horribly, it just means that it's a semantic change, not just a syntactical one). Then there's `HasPlaceholders` which basically is just another semantic one, but with placeholders. The user will have to make some adjustments, but the suggestion still is perfectly valid. rust-analyzer could probably detect those placeholders and put proper "tab through" markers there for the IDE, but that's not necessary for now. Then the last one is `Unspecified` which is so unknown that I don't even know how to judge it, meaning that the suggestion should probably also just be suggested to the user and then they can decide. So with all that in mind, I'm proposing to get rid of the check for Applicability entirely.
* Merge #7507bors[bot]2021-02-011-0/+4
|\ | | | | | | | | | | | | | | 7507: Explain what to do if a release fails r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * Explain what to do if a release failsLaurențiu Nicola2021-02-011-0/+4
| |
* | Merge #7506bors[bot]2021-02-0110-96/+161
|\ \ | |/ |/| | | | | | | | | | | | | | | 7506: Use block_def_map in body lowering r=jonas-schievink a=jonas-schievink This makes `lower_block` update the `DefMap` and `ModuleId` used by the expander to the corresponding `block_def_map`. This cleans up a bit of code, but doesn't expose any new features. bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * Shortcut `block_def_map` if there's no inner itemsJonas Schievink2021-02-011-2/+4
| | | | | | | | | | This previously didn't work, but apparently only because of the wonky test setup
| * Use body lowering for block_def_map testsJonas Schievink2021-02-013-68/+117
| | | | | | | | Removes the hacky and buggy custom lowering code
| * Use block_def_map in body loweringJonas Schievink2021-02-016-26/+40
|/
* Merge #7503bors[bot]2021-01-312-1/+25
|\ | | | | | | | | | | | | | | 7503: Return inner attributes of outline mod declarations in `attrs_query` r=jonas-schievink a=Veykril Co-authored-by: Lukas Wirth <[email protected]>
| * Return inner attributes of outline mod declarations in `attrs_query`Lukas Wirth2021-01-312-1/+25
| |
* | Merge #7502bors[bot]2021-01-312-8/+23
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 7502: Honor #![macro_use] in mod source files r=jonas-schievink a=Veykril Fixes #7501 Since `ItemTree` builds the `RawAttrs` directly we need the special check here as I don't think we can fix this in `RawAttrs` constructor as its solely AST based and we need to touch two different ASTs here. This just made me realize that `attrs_query` suffers from a similar problem, for example hovering an outline `mod` decl won't show inner docs, only outer ones, #7503. Co-authored-by: Lukas Wirth <[email protected]>
| * Honor #![macro_use] in mod source filesLukas Wirth2021-01-312-8/+23
|/
* Merge #7500bors[bot]2021-01-301-2/+19
|\ | | | | | | | | | | | | | | | | | | 7500: Fix ast::String::value not properly escaping in some cases r=Veykril a=Veykril Fixes #7496 bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Fix ast::String::value not properly escaping in some casesLukas Wirth2021-01-301-2/+19
| |
* | Merge #7483bors[bot]2021-01-305-27/+59
|\ \ | |/ |/| | | | | | | | | | | 7483: Classify function calls as functions when shadowed by types r=matklad a=Veykril Fixes #7479 Co-authored-by: Lukas Wirth <[email protected]>
| * Prefer ValueNS when resolving hir path for PathExpressionsLukas Wirth2021-01-291-14/+31
| |
| * Classify function calls as functions when shadowed by typesLukas Wirth2021-01-285-16/+31
| |
* | Merge #7494bors[bot]2021-01-304-74/+71
|\ \ | | | | | | | | | | | | | | | | | | | | | 7494: Simpilfy mbe parsing r=edwin0cheng a=edwin0cheng bors r+ Co-authored-by: Edwin Cheng <[email protected]>
| * | Simpilfy mbe parsingEdwin Cheng2021-01-304-74/+71
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 12:57:14 +0000