aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | 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
* | Avoid using ModPath's fields directlyJonas Schievink2021-02-043-8/+9
| |
* | Make `ModPath`'s representation privateJonas Schievink2021-02-0418-51/+70
| |
* | Intern `TypeRef`s in the containing `ItemTree`Jonas Schievink2021-02-044-21/+67
| |
* | Expander: store a LocalModuleId, not ModuleIdJonas Schievink2021-02-042-14/+11
| | | | | | | | | | It already stores the DefMap containing the module, so having a full ModuleId is unnecessary and makes it easier to mix things up
* | Don't keep the parent DefMap alive via ArcJonas Schievink2021-02-045-36/+67
| | | | | | | | | | This seems like it could easily leak a lot of memory since we don't currently run GC
* | Split out ItemScope::dump from DefMap::dumpJonas Schievink2021-02-032-21/+26
| |
* | Merge #7546bors[bot]2021-02-032-0/+11
|\ \ | | | | | | | | | | | | | | | | | | | | | 7546: Add newline between block and crate maps r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | Add newline between block and crate mapsJonas Schievink2021-02-032-0/+11
| | |
* | | Add a FIXME to ItemTreeJonas Schievink2021-02-031-0/+1
|/ /
* | Update `DefMap` and `block_def_map` docsJonas Schievink2021-02-032-1/+25
| |
* | Merge #7541bors[bot]2021-02-0312-100/+211
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7541: Use block_def_map in body lowering (third time's the charm) r=jonas-schievink a=jonas-schievink After https://github.com/rust-analyzer/rust-analyzer/pull/7380 and https://github.com/rust-analyzer/rust-analyzer/pull/7506 both had to be reverted, this should have finally resolved all remaining bugs. Most importantly, the optimization to skip `block_def_map` computation when the block contains no inner items was fixed (which fortunately was simpler than expected). I've ran `analysis-stats` on libstd locally, which works fine, and also ran this PR locally for a short while without issues. Note that this *still* has no (or almost no) user-facing impact, because the rest of r-a still relies on some local item support hacks. bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | Test for name resolution with DefMap shortcutJonas Schievink2021-02-031-0/+33
| | |
| * | Shortcut `block_def_map` if there's no inner itemsJonas Schievink2021-02-035-11/+26
| | | | | | | | | | | | | | | This previously didn't work, but apparently only because of the wonky test setup
| * | Use body lowering for block_def_map testsJonas Schievink2021-02-033-68/+117
| | | | | | | | | | | | Removes the hacky and buggy custom lowering code
| * | Use block_def_map in body loweringJonas Schievink2021-02-036-26/+40
| | |
* | | Add cargo file tidy testEdwin Cheng2021-02-031-2/+2
|/ /
* / Make sure normal dependencies always have versionPavan Kumar Sunkara2021-02-031-1/+1
|/
* 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)
* Bump rustc_lexerLaurențiu Nicola2021-02-021-1/+1
|
* Bump chalkLaurențiu Nicola2021-02-022-5/+5
|
* Use non-deprecated memmap2 cratekjeremy2021-02-022-2/+2
| | | | | | | `cargo audit` complains that `memmap` is unmaintained so switch to RazrFalcon's maintained version. Removes yet another edge on winapi
* Show alias underlying typelumenian2021-02-021-1/+5
|
* Use the right `DefMap` when looking up modulesJonas Schievink2021-02-023-2/+20
|
* Revert "Use block_def_map in body lowering"Jonas Schievink2021-02-0210-161/+96
|
* Only allow one proc-macro processEdwin Cheng2021-02-011-14/+16
|
* Reap proc macro server instancesLaurențiu Nicola2021-02-012-8/+4
|
* 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.
* 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
| |
* | 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
| | |
* | | Add --print-config-schema to helpLaurențiu Nicola2021-01-291-0/+2
|/ /
* | Simplify mbe match error.Edwin Cheng2021-01-296-210/+180
| | | | | | | | Handle parse error in rule parsing instead of match in mbe
* | Rename mbe_expander for consistencyEdwin Cheng2021-01-294-5/+5
| |
* | Forbid flyimport completions in use statementsKirill Bulatov2021-01-281-1/+22
| |
* | Fix incorrect `FileId` and remove broken shortcutJonas Schievink2021-01-282-16/+9
| | | | | | | | | | Apparently we were using the crate's root file instead of the file containing the block.
* | Merge #7482bors[bot]2021-01-281-0/+63
|\ \ | | | | | | | | | | | | | | | | | | | | | 7482: block_def_map: add a few macro tests r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | block_def_map: add a few macro testsJonas Schievink2021-01-281-0/+63
| | |
* | | Merge #7412bors[bot]2021-01-2811-199/+397
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7412: Async loading for outdir and proc-macro r=maklad a=edwin0cheng cc #7328 ![Peek 2021-01-24 02-04](https://user-images.githubusercontent.com/11014119/105610083-8f208100-5de8-11eb-8e96-c2d4e349b352.gif) [Edit] ~~Finding a way to know when the workspace and build data are loaded...~~ [Edit 2] Not perfect solution, but seem to work now. Co-authored-by: Edwin Cheng <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 08:20:29 +0000