-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Stabilize const_cell_into_inner. #84087
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
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
Looks like rustc disagrees with our decision to make these const. :) cc @rust-lang/wg-const-eval |
Looks like this is blocked on the "precise drop analysis" unstable const feature (#73255). |
☔ The latest upstream changes (presumably #87768) made this pull request unmergeable. Please resolve the merge conflicts. |
Can we stabilize |
Considering that all that is missing is a review of rust-lang/rustc-dev-guide#1240 followed by the immediate stabilization of precise const drops, we should probably just wait for that |
d938ac3
to
272fda6
Compare
272fda6
to
c46a49b
Compare
So, turns out #73255 actually has some blockers (the FCP is cancelled). So I'm raising the same question again: Can we stabilize |
☔ The latest upstream changes (presumably #91962) made this pull request unmergeable. Please resolve the merge conflicts. |
👋 Hello, I'm writing this comment in this stabilization PR to notify you, the authors of this PR, that #100591 has been merged, which implemented a change in how features are stabilized. Your PR has been filed before the change, so will likely require modifications in order to comply with the new rules. I recommend you to:
That's it! The If you have any questions, feel free to drop by the zulip stream, or ping me directly in this PR's thread. Thanks! 👋 |
FCP finished here: #78729 (comment)
blocked on "precise drop analysis" unstable const feature (#73255).
closes #78729