-
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
Properly feature gate all unstable ABIs #34904
Conversation
@petrochenkov to be honest I was expecting a warning cycle. For now I'll at least tag this as needing a crater run. |
I'd be surprised if it broke anything in practice, but let's see what crater will say. |
The patch itself looks fine, so r=me apart from the question of whether it should go through a warning cycle. I'll nominate for discussion at lang team mtg. |
Will start a crater run now. Sorry about that, we had network issues with GitHub for a while. |
Crater report shows 0 regressions. |
OK, let's do it. |
@bors r+ |
📌 Commit 9292c0b has been approved by |
@bors: rollup assuming this isn't very platform-specific and green travis means it's good to go whenever |
Properly feature gate all unstable ABIs Fixes rust-lang#34900 [breaking-change] r? @pnkfelix --- Function-visiting machinery for AST/HIR is surprisingly error-prone, it's *very* easy to miss some cases or visit something twice while writing a visitor. This is the true problem behind rust-lang#34900. I'll try to restructure these visitors a bit and send one more PR later.
Properly feature gate all unstable ABIs Fixes #34900 [breaking-change] r? @pnkfelix --- Function-visiting machinery for AST/HIR is surprisingly error-prone, it's *very* easy to miss some cases or visit something twice while writing a visitor. This is the true problem behind #34900. I'll try to restructure these visitors a bit and send one more PR later.
Fixes #34900
[breaking-change]
r? @pnkfelix
Function-visiting machinery for AST/HIR is surprisingly error-prone, it's very easy to miss some cases or visit something twice while writing a visitor. This is the true problem behind #34900. I'll try to restructure these visitors a bit and send one more PR later.