Skip to content

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

Merged
merged 85 commits into from
Jun 18, 2025
Merged

Subtree update of rust-analyzer #142567

merged 85 commits into from
Jun 18, 2025

Conversation

lnicola
Copy link
Member

@lnicola lnicola commented Jun 16, 2025

r? @ghost

regexident and others added 30 commits June 6, 2025 09:45
`#[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
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] <support@github.com>
…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
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 16, 2025
@rustbot
Copy link
Collaborator

rustbot commented Jun 16, 2025

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

@lnicola
Copy link
Member Author

lnicola commented Jun 16, 2025

@bors r+ p=1 subtree sync

@bors
Copy link
Collaborator

bors commented Jun 16, 2025

📌 Commit 36f2e8f has been approved by lnicola

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 16, 2025
@bors
Copy link
Collaborator

bors commented Jun 17, 2025

⌛ Testing commit 36f2e8f with merge 2113b26...

bors added a commit that referenced this pull request Jun 17, 2025
Subtree update of `rust-analyzer`

r? `@ghost`
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented Jun 17, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jun 17, 2025
@lnicola
Copy link
Member Author

lnicola commented Jun 17, 2025

@bors2 try

@rust-bors
Copy link

rust-bors bot commented Jun 17, 2025

⌛ Trying commit 6a9c5d7 with merge 0904302

To cancel the try build, run the command @bors2 try cancel.

rust-bors bot added a commit that referenced this pull request Jun 17, 2025
Subtree update of `rust-analyzer`

r? `@ghost`
@rust-bors
Copy link

rust-bors bot commented Jun 17, 2025

☀️ Try build successful (CI)
Build commit: 0904302 (090430278b1a42dc9d9aaccaf177e66d6e2b0808, parent: 55d436467c351b56253deeba209ae2553d1c243f)

@lnicola
Copy link
Member Author

lnicola commented Jun 17, 2025

@bors r+

@bors
Copy link
Collaborator

bors commented Jun 17, 2025

📌 Commit 6a9c5d7 has been approved by lnicola

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 17, 2025
@bors
Copy link
Collaborator

bors commented Jun 17, 2025

⌛ Testing commit 6a9c5d7 with merge 27eb269...

@bors
Copy link
Collaborator

bors commented Jun 18, 2025

☀️ Test successful - checks-actions
Approved by: lnicola
Pushing 27eb269 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 18, 2025
@bors bors merged commit 27eb269 into rust-lang:master Jun 18, 2025
11 checks passed
@rustbot rustbot added this to the 1.89.0 milestone Jun 18, 2025
Copy link
Contributor

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 differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 27eb2690f4d78f0f41eaa7193a06cd49d74b2eb0 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-apple-2: 5696.4s -> 3645.1s (-36.0%)
  2. x86_64-apple-1: 8660.8s -> 6518.2s (-24.7%)
  3. i686-gnu-2: 6339.0s -> 5412.2s (-14.6%)
  4. i686-gnu-1: 8289.0s -> 7231.0s (-12.8%)
  5. i686-gnu-nopt-1: 8043.7s -> 7042.8s (-12.4%)
  6. dist-apple-various: 6234.5s -> 6981.0s (12.0%)
  7. x86_64-rust-for-linux: 2914.9s -> 2571.6s (-11.8%)
  8. x86_64-gnu-llvm-19-1: 3664.0s -> 3256.2s (-11.1%)
  9. armhf-gnu: 5096.1s -> 4542.0s (-10.9%)
  10. mingw-check-tidy: 75.4s -> 67.2s (-10.8%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (27eb269): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This 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.

Cycles

Results (primary -1.6%, secondary -2.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.6% [-1.6%, -1.6%] 1
Improvements ✅
(secondary)
-2.9% [-4.6%, -1.6%] 10
All ❌✅ (primary) -1.6% [-1.6%, -1.6%] 1

Binary size

Results (secondary 0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.0% [0.0%, 0.0%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Bootstrap: 692.654s -> 693.336s (0.10%)
Artifact size: 372.15 MiB -> 372.12 MiB (-0.01%)

@lnicola lnicola deleted the sync-from-ra branch June 18, 2025 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.