-
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
Turn deprecation lint legacy_imports
into a hard error
#50760
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
Seems reasonable. =) Do we feel the need to do a final "cargo check" crater run? (So we can cc the relevant people) |
OTOH if previous runs found no regressions, and we are deny by default, seems like overkill. |
@bors r+ |
📌 Commit d1b0274 has been approved by |
⌛ Testing commit d1b0274 with merge 413bc952821db174ec08d4338f7fbbc2ec468124... |
💔 Test failed - status-appveyor |
@bors retry
1 second is not enough for the OS to close the port? |
Turn deprecation lint `legacy_imports` into a hard error Closes #38260 The lint was introduced in Dec 2016, then made deny-by-default in Jun 2017 when crater run found 0 regressions caused by it. This lint requires some not entirely trivial amount of import resolution logic that (surprisingly or not) interacts with `feature(use_extern_macros)` (#35896), so it would be desirable to remove it before stabilizing `use_extern_macros`. In particular, this PR fixes the failing example in #50725 (but not the whole issue, `use std::panic::{self}` still can cause other undesirable errors when `use_extern_macros` is enabled).
☀️ Test successful - status-appveyor, status-travis |
Closes #38260
The lint was introduced in Dec 2016, then made deny-by-default in Jun 2017 when crater run found 0 regressions caused by it.
This lint requires some not entirely trivial amount of import resolution logic that (surprisingly or not) interacts with
feature(use_extern_macros)
(#35896), so it would be desirable to remove it before stabilizinguse_extern_macros
.In particular, this PR fixes the failing example in #50725 (but not the whole issue,
use std::panic::{self}
still can cause other undesirable errors whenuse_extern_macros
is enabled).