-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Improve detection of unused imports (fixes #30078) #30325
Conversation
r? @jroesch (rust_highfive has picked a reviewer for you, use r? to override) |
Travis failed because of new unused_imports warnings. |
797acf3
to
9a88b11
Compare
Awesome! Could you also expand the commit message to include information like:
r? @nrc (looking at other resolve changes lately as well) |
3651c06
to
83dde14
Compare
r+ with the changes to the commit message that @alexcrichton requested |
Eh, isn't the commit message already changed? |
@bors: r+ (ah yeah, I think I needed to refresh my browser) |
📌 Commit 83dde14 has been approved by |
This fixes a bug in which unused imports can get wrongly marked as used when checking for unused qualifications in `resolve_path` (issue rust-lang#30078), and it removes unused imports that were previously undetected because of the bug.
☔ The latest upstream changes (presumably #30300) made this pull request unmergeable. Please resolve the merge conflicts. |
…ed as used when checking for unused qualifications in resolve_path (fixes rust-lang#30078)
83dde14
to
ba20a86
Compare
@nrc rebased |
@bors: r+ |
📌 Commit ba20a86 has been approved by |
This fixes a bug in which unused imports can get wrongly marked as used when checking for unused qualifications in `resolve_path` (issue #30078), and it removes unused imports that were previously undetected because of the bug.
This fixes a bug in which unused imports can get wrongly marked as used when checking for unused qualifications in
resolve_path
(issue #30078), and it removes unused imports that were previously undetected because of the bug.