Skip to content

resolve: Do not finalize shadowed bindings #145113

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

petrochenkov
Copy link
Contributor

I.e. do not mark them as used, or non-speculative loaded, or similar.
Previously they were sometimes finalized during early resolution, causing issues like #144793 (comment).

I.e. do not mark them as used, or non-speculative loaded, or similar.
Previously they were sometimes finalized during early resolution, causing issues like rust-lang#144793 (comment).
@rustbot
Copy link
Collaborator

rustbot commented Aug 8, 2025

r? @BoxyUwU

rustbot has assigned @BoxyUwU.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Aug 8, 2025
@rust-log-analyzer
Copy link
Collaborator

The job aarch64-gnu-llvm-19-1 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@compiler-errors
Copy link
Member

Looks like this triggers a new unused warning in the stdlib? Is this intentional? We probably should crater this if so.

@bors2 try
@rustbot author

@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 8, 2025
@rustbot
Copy link
Collaborator

rustbot commented Aug 8, 2025

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@rustbot rustbot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Aug 8, 2025
@rust-bors
Copy link

rust-bors bot commented Aug 8, 2025

⌛ Trying commit 5feb92e with merge 8c500c7

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

rust-bors bot added a commit that referenced this pull request Aug 8, 2025
resolve: Do not finalize shadowed bindings
@petrochenkov
Copy link
Contributor Author

petrochenkov commented Aug 8, 2025

Looks like this triggers a new unused warning in the stdlib? Is this intentional?

Yes, some new unused items can be detected now.
It shouldn't be common though.

@rust-bors
Copy link

rust-bors bot commented Aug 8, 2025

☀️ Try build successful (CI)
Build commit: 8c500c7 (8c500c7cefd54fd11d57295f3771d576be9ee415, parent: 2886b36df4a646dd8d82fb65bf0c9d8d96c1f71a)

@BoxyUwU BoxyUwU removed their assignment Aug 8, 2025
@petrochenkov
Copy link
Contributor Author

We probably should crater this if so.

@craterbot check

@craterbot
Copy link
Collaborator

👌 Experiment pr-145113 created and queued.
🤖 Automatically detected try build 8c500c7
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Aug 8, 2025
@craterbot
Copy link
Collaborator

🚧 Experiment pr-145113 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@compiler-errors compiler-errors self-assigned this Aug 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-crater Status: Waiting on a crater run to be completed. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants