Add Vec::get_uninit_unchecked #70967
Closed
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
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @joshtriplett (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
rust-highfive
added
the
S-waiting-on-review
This comment has been minimized.
This comment has been minimized.
moshg
force-pushed
the
get_uninit
branch
2 times, most recently
from
04c9896 to
0348abf
Compare
This comment has been minimized.
This comment has been minimized.
moshg
force-pushed
the
get_uninit
branch
2 times, most recently
from
fe80faa to
2225c47
Compare
Centril
reviewed
Apr 10, 2020
src/liballoc/vec.rs
Outdated
| /// assert_eq!(&*x, &[0, 1, 2, 3]); | ||
| /// ``` | ||
| #[unstable(feature = "vec_get_uninit_unchecked", issue = "none")] | ||
| pub fn get_uninit_unchecked(&mut self, index: usize) -> &mut MaybeUninit<T> { |
There was a problem hiding this comment.
Suggested change
| pub fn get_uninit_unchecked(&mut self, index: usize) -> &mut MaybeUninit<T> { | |
| pub unsafe fn get_uninit_unchecked(&mut self, index: usize) -> &mut MaybeUninit<T> { |
There are two ways in which you can violate soundness with this method:
- You provide
indexwhereindex >= self.capacity(). - You do
let elem = vec.get_uninit_unchecked(index); *elem = MaybeUninit::uninit(); drop(vec[index]);.
There was a problem hiding this comment.
Also, you can have a memory leak if you forget to use vec.set_len(...) afterwards in some circumstances; also worth noting in docs.
Centril
added
S-waiting-on-author
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
joshtriplett
added
the
T-libs-api
|
Tagging libs, and assigning to a random libs team member. |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
…g* Improve the explanation in the assertion* UB and memory leak notes
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
@Centril Thank you for your review! I cannot find broken links. How can I find them? With |
|
Rather than conflating unchecked indexing and conversion to impl<T> Vec<T> {
/// Returns the vector's spare capacity as a mutable slice of maybe-uninitialized values.
///
/// The length of the slice will be `self.capacity() - self.len()`.
pub fn spare_capacity_mut(&mut self) -> &mut [MaybeUninit<T>] { ... }
} |
joelpalmer
removed
the
S-waiting-on-author
joelpalmer
added
the
S-waiting-on-author
|
Ping from Triage: Hi @moshg - any updates? |
joelpalmer
added
S-waiting-on-author
|
Ping from Triage: Closing due to inactivity. @moshg please reopen with updates. Thanks for the PR. |
Manishearth
added a commit
to Manishearth/rust
that referenced
this pull request
Aug 2, 2020
Add Vec::spare_capacity_mut Returns the remaining spare capacity of the vector as a slice of `MaybeUninit<T>`. As suggested by @sfackler in rust-lang#70967 (comment). r? @sfackler
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.
This is intended to reduce misusing
get_unchecked_mutto access out of bounds.In addition, we can detect out-of-allocation with this method unlike
x.as_ptr_mut().add(index).I hope this to help
get_uncheckedto do bound check in debug build in the future. #36976Though immutable
get_uninit_uncheckedis useless, should I nameget_uninit_unchecked_mut?