-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Allow unused extern crate again #44825
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
This is a partial revert of rust-lang#42588. There is a usability concern reported in rust-lang#44294 that was not considered in the discussion of the PR, so I would like to back this out of 1.21. As is, I think users would have a worse and more confusing experience with this lint enabled by default. We can re-enabled once there are better diagnostics or the case in rust-lang#44294 does not trigger the lint.
r? @arielb1 (rust_highfive has picked a reviewer for you, use r? to override) |
This area, both error messages and imports, is changing very rapidly. I think @aturon is taking the lead on imports - what do you think of disabling the lint? |
r? @aturon |
I had to disable the lint in multiple occasions in my code due to false positives of it... so definitely a 👍 from me. I'm not annoyed that I have to The issue (false positives connected to linking) has been discussed here before. EDIT: I've opened #44827 to discuss my suggestion. I'd also say that there is probably another question to discuss which is how to handle the lint in the future when |
Could we stop triggering the lint for crates with |
@bors: r+ |
📌 Commit 247b58b has been approved by |
@bors: p=1 this is likely to be beta-accepted |
Allow unused extern crate again This is a partial revert of #42588. There is a usability concern reported in #44294 that was not considered in the discussion of the PR, so I would like to back this out of 1.21. As is, I think users would have a worse and more confusing experience with this lint enabled by default. We can re-enabled once there are better diagnostics or the case in #44294 does not trigger the lint.
☀️ Test successful - status-appveyor, status-travis |
Marking as beta-accepted. Small issue. cc @rust-lang/compiler |
Backporting now. |
Beta 20170928 Backports of: - Allow unused extern crate again #44825 - macros: fix bug in collecting trait and impl items with derives. #44757 - `--cap-lints allow` switches off `can_emit_warnings` #44627 - Update the libc submodule #44116 - limit and clear cache obligations opportunistically #44269 - clear out projection subobligations after they are processed #43999
Beta 20170928 Backports of: - Allow unused extern crate again #44825 - macros: fix bug in collecting trait and impl items with derives. #44757 - `--cap-lints allow` switches off `can_emit_warnings` #44627 - Update the libc submodule #44116 - limit and clear cache obligations opportunistically #44269 - clear out projection subobligations after they are processed #43999 - fix logic error in #44269's `prune_cache_value_obligations` #45065 - REVERTS #43543: Cleanup some remains of `hr_lifetime_in_assoc_type` compatibility lint:
This is a partial revert of #42588. There is a usability concern reported in #44294 that was not considered in the discussion of the PR, so I would like to back this out of 1.21. As is, I think users would have a worse and more confusing experience with this lint enabled by default. We can re-enabled once there are better diagnostics or the case in #44294 does not trigger the lint.