-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[beta] Revert #113923 #119886
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
[beta] Revert #113923 #119886
Conversation
|
The Miri subtree was changed cc @rust-lang/miri |
@rustbot label +beta-nominated +beta-accepted |
@rustbot label +beta-nominated |
I've created another beta backport PR #120111. Feel free to roll them up :) |
Procedural note: we normally deal with backport flags on the master PR, especially because it doesn't show up in the release team's queries until merged. That's kind of a chicken-and-egg situation when you're already targeting beta. Then we may ask for help backporting if there's some conflict, but generally we can handle it. :) https://forge.rust-lang.org/release/backporting.html Anyway, no worries, I've verified that this is a clean match of #119885. @bors r+ rollup=never |
Thanks, I got it. I just need to add the |
☀️ Test successful - checks-actions |
Per #t-compiler/meetings > [weekly] 2024-01-11 discussion, revert #113923. Also revert associated #118568.
The PR #113923 causes the regression issue #118609. We need more time to find a proper solution.
Discussions start at 412365838 and continue to 412369643.
Fixes #118609.
Same as #119885 but backported to beta.
r? compiler