-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
[WIP] BARE_TRAIT_OBJECTS -> Deny #59482
Conversation
Before I |
I'm probably not the most reasonable choice for a reviewer here as I'm strongly of the opinion that lints are but sound and smoke. Irrelevant of the "fallout" (in quotes, because it doesn't break dependencies, is trivial to fix, even rustfixable), I think we should just merge this. Going through a warning phase is pretty useless, as (subjectively, I have no data) Rust developers don't really commit (or at least publish) code that has warnings. |
@oli-obk Oh hmm... the lint is Allow right now tho so it generates no warnings. Let's discuss on Thursday's T-Lang meeting and see how we feel about jumping straight to |
Regarding all of these |
@jethrogb This is specified in https://github.com/rust-lang/rfcs/blob/master/text/2113-dyn-trait-syntax.md#migration. This is just executing the already agreed-to plan. (And we decided that we would wait with ramping up the idioms lints until later into the edition) |
RFC 2113 just covers this PR, what about the other 3? Also it seems bad to change a lint from allow to deny without a warning period. |
@jethrogb Left comments on those.
Please see the first comment in the PR. The idea is to measure the impact and deciding how to proceed from there. |
We discussed this on this weeks lang meeting; the general consensus was to crater and see how things fall out and move on from there. |
ping from triage, closing this due to inactivity |
Based on https://github.com/rust-lang/rfcs/blob/master/text/2113-dyn-trait-syntax.md#migration.
Let's first crater this for both editions to see what the fallout is. (I expect it will be large)
I suspect the likely outcome will be
Warn
on at least Rust 2015 for a start.r? @oli-obk