-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Subtree update of rust-analyzer
#142567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subtree update of rust-analyzer
#142567
Conversation
`#[cfg_attr]` is a builtin attr, but it may still contain a macro.
…-two Make `Semantics<'db, DB>` support `Semantics<'db, dyn HirDatabase>`, take two
…items fix: Do not error at impls for unsized types that do not include `where Self: Sized` items
[minor] Fix typos
It used to decompose them thinking they were numbers.
…v-minus fix: Fix proc macro server handling of strings with minuses
fix: Hide dyn inlay hints for incomplete `impl`s
…trait-solve-invalidation hir-ty: test incremental trait solving
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 1.1.11 to 1.1.12. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@1.1.11...v1.1.12) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 1.1.12 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…yarn/editors/code/brace-expansion-1.1.12 chore(deps-dev): bump brace-expansion from 1.1.11 to 1.1.12 in /editors/code
fix: Fix completion with some attribute macros
Instead of simple numbering, we hash important bits, like the name of the item. This will allow for much better incrementality, e.g. when you add an item. Currently, this invalidates the IDs of all following items, which invalidates pretty much everything.
Item tree IDs are very unstable (adding an item of a kind invalidates all following items of the same kind). Instead use ast ids, which, since the previous commit, are pretty stable.
I'm joking, but now that the def map is the only thing that uses the item tree, we can remove a lot of things from it that aren't needed for the def map.
We can do that and it's pretty heavy.
Provide better incrementality when items are changed
Doing so can cause us to duplicate navigation targets for the same ranges which breaks convenience features of some editors where go to def can trigger find all references
`ItemTree`'s `ItemVisibilities` has no identity, so deduplicate
fix: Do not force descend into derives for goto IDE features
rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
@bors r+ p=1 subtree sync |
Subtree update of `rust-analyzer` r? `@ghost`
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors2 try |
Subtree update of `rust-analyzer` r? `@ghost`
@bors r+ |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing f3db639 (parent) -> 27eb269 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 27eb2690f4d78f0f41eaa7193a06cd49d74b2eb0 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (27eb269): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (primary -1.6%, secondary -2.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 692.654s -> 693.336s (0.10%) |
r? @ghost