-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Stabilize const_maybe_uninit_write
#131713
Stabilize const_maybe_uninit_write
#131713
Conversation
The other methods from #63567 have already been stabilized, but this needs FCP. I will be able to drop the enable for |
☔ The latest upstream changes (presumably #131887) made this pull request unmergeable. Please resolve the merge conflicts. |
1ed32c5
to
7808838
Compare
Cc @rust-lang/wg-const-eval for this one as well |
There is something odd about the diff (at least on mobile), it seems to say the "stable" line changed as well...
EDIT: Ah, it got moved around, the diff was just hard to read on the small screen.
But looks good from a const eval side!
|
@rust-lang/libs-api could someone start FCP? :) Should be uncontroversial, the function has been stable for a while and this just makes it const-stable. |
@rfcbot fcp merge |
Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
@BurntSushi @joshtriplett @m-ou-se friendly FCP checkbox reminder :) |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
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. |
FCP passed, should be good to go then. :) @bors r+ rollup |
☔ The latest upstream changes (presumably #133728) made this pull request unmergeable. Please resolve the merge conflicts. |
Timing… I’ll get that soon |
Mark the following API const stable: impl<T> MaybeUninit<T> { pub const fn write(&mut self, val: T) -> &mut T; } This depends on `const_mut_refs` and `const_maybe_uninit_assume_init`, both of which have recently been stabilized. Tracking issue: <rust-lang#63567>
7808838
to
c5fedc2
Compare
r=me when CI is green |
@bors r=RalfJung,dtolnay |
…llaumeGomez Rollup of 10 pull requests Successful merges: - rust-lang#131713 (Stabilize `const_maybe_uninit_write`) - rust-lang#133535 (show forbidden_lint_groups in future-compat reports) - rust-lang#133610 (Move `Const::{from_anon_const,try_from_lit}` to hir_ty_lowering) - rust-lang#133701 (Use c"lit" for CStrings without unwrap) - rust-lang#133704 (fix ICE when promoted has layout size overflow) - rust-lang#133705 (add "profiler" and "optimized-compiler-builtins" option coverage for ci-rustc) - rust-lang#133710 (Reducing `target_feature` check-cfg merge conflicts) - rust-lang#133732 (Fix `-Zdump-mir-dataflow`) - rust-lang#133746 (Change `AttrArgs::Eq` to a struct variant) - rust-lang#133763 (Fix `f16::midpoint` const feature gate) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#131713 - tgross35:stabilize-const_maybe_uninit_write, r=RalfJung,dtolnay Stabilize `const_maybe_uninit_write` Mark the following API const stable: ```rust impl<T> MaybeUninit<T> { pub const fn write(&mut self, val: T) -> &mut T; } ``` This depends on `const_mut_refs` and [`const_maybe_uninit_assume_init`](rust-lang#86722), both of which have recently been stabilized. Closes: <rust-lang#63567>
Mark the following API const stable:
This depends on
const_mut_refs
andconst_maybe_uninit_assume_init
, both of which have recently been stabilized.Closes: #63567
r? libs-api