-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
discard default auto trait impls if explicit ones exist #85048
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
don't have the capacity to work on this rn |
…i-obk extend `simplify_type` might cause a slight perf inprovement and imo more accurately represents what types there are. considering that I was going to use this in rust-lang#85048 it seems like we might need this in the future anyways 🤷
This comment has been minimized.
This comment has been minimized.
f3d243d
to
a477613
Compare
@craterbot check |
@craterbot ping |
🏓 Pong! ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
@craterbot check |
🚨 Error: missing start toolchain 🆘 If you have any trouble with Crater please ping |
woops @bors try |
⌛ Trying commit a4776138bb4707af42c3f3a5c56d7ae3005ee406 with merge dc0340a3a9e4e041da9a5966db8733ccb7ac87e0... |
☀️ Try build successful - checks-actions |
@craterbot check |
🚨 Error: experiment 'pr-85048-2' not found 🆘 If you have any trouble with Crater please ping |
@craterbot run name=pr-85048-2 start=stable end=try#a0aab45a34400a5afa9e3246429a7455540b55d2 mode=check-only crates=https://crater-reports.s3.amazonaws.com/pr-85048/retry-regressed-list.txt |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
@lcnr and I discussed this today. Our conclusion was that while we do believe this PR should land, and it fixes a bug in the auto trait implementation that gave it unexpected semantics, we don't feel good about breaking the Two possible ways to resolve this:
Either would permit a second impl like @lcnr talked about modifying the PR to land as a future compatibility warning in the meantime. |
@craterbot edit p=5 |
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ping |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
alright, so we're left with only the expected auto trait fallout. Going to write a lint for that in a different pr for now. |
implement a lint for suspicious auto trait impls cc rust-lang#85048 (comment) r? `@nikomatsakis`
implement a lint for suspicious auto trait impls cc rust-lang#85048 (comment) r? ``@nikomatsakis``
implement a lint for suspicious auto trait impls cc rust-lang#85048 (comment) r? `@nikomatsakis`
implement a lint for suspicious auto trait impls cc rust-lang#85048 (comment) r? ``@nikomatsakis``
we could also just merge the breakage in the same version as the lint ✨ would prefer that tbh :( |
discard default auto trait impls if explicit ones exist (rebase of rust-lang#85048) Rebase of rust-lang#85048
discard default auto trait impls if explicit ones exist (rebase of rust-lang#85048) Rebase of rust-lang#85048
fixes #84857
definitely still far from being UwU
When implementing an auto trait for
&'a SomeType
that auto trait is now not implemented for&&T
which is unfortunate xxr? @nikomatsakis