-
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
rustc: Suggest removing extern crate
in 2018
#53684
Conversation
r? @oli-obk (rust_highfive has picked a reviewer for you, use r? to override) |
Could we add a test for when the crate is used only through macros, both in the |
r=me with @Mark-Simulacrum 's tests |
This commit updates the `unused_extern_crates` lint to make automatic suggestions about removing `extern crate` annotations in the 2018 edition. This ended up being a little easier than originally though due to what's likely been fixed issues in the resolver! Closes rust-lang#52829
99f46ed
to
51fd3bf
Compare
Good idea @Mark-Simulacrum! While the resulting code isn't fantastic, it's reasonable in the sense it produces no warnings. I'll file a follow-up issue. @bors: r=oli-obk |
📌 Commit 51fd3bf has been approved by |
I've filed #53741 as a follow-up |
rustc: Suggest removing `extern crate` in 2018 This commit updates the `unused_extern_crates` lint to make automatic suggestions about removing `extern crate` annotations in the 2018 edition. This ended up being a little easier than originally though due to what's likely been fixed issues in the resolver! Closes rust-lang#52829
rustc: Suggest removing `extern crate` in 2018 This commit updates the `unused_extern_crates` lint to make automatic suggestions about removing `extern crate` annotations in the 2018 edition. This ended up being a little easier than originally though due to what's likely been fixed issues in the resolver! Closes #52829
☀️ Test successful - status-appveyor, status-travis |
This commit updates the
unused_extern_crates
lint to make automaticsuggestions about removing
extern crate
annotations in the 2018 edition. Thisended up being a little easier than originally though due to what's likely been
fixed issues in the resolver!
Closes #52829