MaybeUninit array cleanup #96099
Merged
MaybeUninit array cleanup #96099
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Links MaybeUninit::uninit_array to meta-tracking issue * Links MaybeUninit::array_assume_init to meta-tracking issue * Unstably constifies MaybeUninit::array_assume_init
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
r? @thomcc (rust-highfive has picked a reviewer for you, use r? to override) |
This was referenced Apr 16, 2022
|
This unstably r? rust-lang/libs-api @rustbot label +T-libs-api -T-lib |
|
@bors r+ |
|
📌 Commit 63a8652 has been approved by |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 16, 2022
Rollup of 9 pull requests Successful merges: - rust-lang#93969 (Only add codegen backend to dep info if -Zbinary-dep-depinfo is used) - rust-lang#94605 (Add missing links in platform support docs) - rust-lang#95372 (make unaligned_references lint deny-by-default) - rust-lang#95859 (Improve diagnostics for unterminated nested block comment) - rust-lang#95961 (implement SIMD gather/scatter via vector getelementptr) - rust-lang#96004 (Consider lifetimes when comparing types for equality in MIR validator) - rust-lang#96050 (Remove some now-dead code that was only relevant before deaggregation.) - rust-lang#96070 ([test] Add test cases for untested functions for BTreeMap) - rust-lang#96099 (MaybeUninit array cleanup) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
yvt
added a commit
to r3-os/r3
that referenced
this pull request
Apr 21, 2022
The `const`-ness of `MaybeUninit::uninit_array` has been split into a separate feature by [rust-lang/rust#96099][1]. [1]: rust-lang/rust#96099
yvt
added a commit
to r3-os/r3
that referenced
this pull request
Apr 23, 2022
The `const`-ness of `MaybeUninit::uninit_array` has been split into a separate feature by [rust-lang/rust#96099][1]. [1]: rust-lang/rust#96099
yvt
added a commit
to r3-os/r3
that referenced
this pull request
May 23, 2022
This feature, which covers the `const fn` version of `MaybeUninit:: array_assume_init`, was added by [rust-lang/rust#96099][1]. [1]: rust-lang/rust#96099
yvt
added a commit
to r3-os/r3
that referenced
this pull request
May 24, 2022
This feature, which covers the `const fn` version of `MaybeUninit:: array_assume_init`, was added by [rust-lang/rust#96099][1]. [1]: rust-lang/rust#96099
yvt
added a commit
to r3-os/r3
that referenced
this pull request
May 24, 2022
This feature, which covers the `const fn` version of `MaybeUninit:: array_assume_init`, was added by [rust-lang/rust#96099][1]. [1]: rust-lang/rust#96099
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MaybeUninit::uninit_arrayto meta-tracking issueMaybeUninit::array_assume_initto meta-tracking issueMaybeUninit::array_assume_initAnother thing worth mentioning: this splits the const feature flag for
maybe_uninit_uninit_arrayintoconst_maybe_uninit_uninit_arrayto avoid weird cases where only one gets stabilised.Note that it may be desired to keep the
array_assume_initmethod linked to its dedicated issue, but at least for now, I decided to link to the meta-tracking issue so that all of the methods lead users to the same place. But I can revert that bit if desired.The meta-tracking issue that I filed is #96097.