Uh oh!
There was an error while loading. Please reload this page.
rustc: Suggest removing extern crate in 2018 - #53684
Conversation
rust-highfive
commented
Aug 24, 2018
r? @oli-obk (rust_highfive has picked a reviewer for you, use r? to override) |
Mark-Simulacrum
commented
Aug 25, 2018
Could we add a test for when the crate is used only through macros, both in the |
oli-obk
commented
Aug 25, 2018
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! Closesrust-lang#52829
99f46ed to
51fd3bfComparealexcrichton
commented
Aug 27, 2018
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 |
bors
commented
Aug 27, 2018
📌 Commit 51fd3bf has been approved by |
alexcrichton
commented
Aug 27, 2018
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! Closesrust-lang#52829
bors
commented
Aug 29, 2018
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
bors
commented
Aug 29, 2018
☀️ Test successful - status-appveyor, status-travis |
This commit updates the
unused_extern_crateslint to make automaticsuggestions about removing
extern crateannotations 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