-
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
Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error #84022
Conversation
@bors try |
⌛ Trying commit 191f8a971b06684f802fcc33a2398bd15df8a3ab with merge 96e388c3ccda74650413d435528d8e0ed2872a21... |
☀️ Try build successful - checks-actions |
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Unfortunately, one of the regressions is in the unmaintained crate https://github.com/MaikKlein/enumflags |
cc @petrochenkov - I'm not sure how you'd like to move forward with this. We could try to move people off https://github.com/MaikKlein/enumflags before we remove the hack, but that would still result in the crate become unusable (the last update was in 2019, and the repository has been archived). |
Leave it as is for a couple more years? |
@Aaron1011 Do you want to turn this into an error on 2021 and later editions only? Or do you prefer this be closed? |
@crlf0710 I think that would be reasonable. While this could theoretically break some 2018 edition code in the presence of a sufficiently weird proc-macro (e.g. a proc-macro which marks the input tokens with a 2021 edition span), I think it would be good to make progress on this issue. |
cc @nagisa @estebank @nikomatsakis @pnkfelix for review and checkboxes |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
3606629
to
7d82cad
Compare
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
@bors r+ |
Rollup of 5 pull requests Successful merges: - rust-lang#84022 (Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error) - rust-lang#103760 (resolve: Turn the binding from `#[macro_export]` into a proper `Import`) - rust-lang#103813 (rustdoc: remove unnecessary CSS `.search-results { clear: both }`) - rust-lang#103817 (rustdoc: rename syntax highlighting CSS class `attribute` to `attr`) - rust-lang#103833 (:arrow_up: rust-analyzer) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
this probably should have been marked as rollup=never |
In particular, I have confirmed that this PR was what injected issue #106337. I'm planning to open a PR reverting this one and beta-nominate it for the 1.67-beta (due for release as 1.67-stable on 2023-01-26) in order to buy us some time to talk about strategies for the macro implementation pattern described in #106337 and in issue #64079 |
…06337, r=Mark-Simulacrum Revert "Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error" This reverts commit 7d82cad aka PR rust-lang#84022 I am doing this to buy us some time with respect to issue rust-lang#106337 w.r.t. the 1.67 release.
r? @ghost