Add a function to turn Box<T> into Box<[T]>#71421
Merged
bors merged 2 commits intorust-lang:masterfrom Apr 26, 2020
Merged
Conversation
Contributor
|
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
Contributor
|
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 |
|
I think it is better to have an issue about this, and also maybe add a test |
elichai
force-pushed
the
2020-04-boxed-slice
branch
from
25175e6 to
4693236
Compare
Contributor
Author
Added tests, is this what you were looking for? (I'm not sure why every error appears twice) |
elichai
force-pushed
the
2020-04-boxed-slice
branch
from
4693236 to
29f7729
Compare
Member
Those are all about the alignment of pointer-like values themselves, regardless of |
Contributor
Author
That makes sense. the usage of |
cuviper
reviewed
Apr 23, 2020
src/liballoc/boxed.rs
Outdated
Member
There was a problem hiding this comment.
AFAIK, trait impls are effectively insta-stable -- they can't really be unstable unless the trait and/or types involved are unstable.
Contributor
Author
There was a problem hiding this comment.
ha, so I'll remove this from, and it can be added back if/when this is stable
elichai
force-pushed
the
2020-04-boxed-slice
branch
from
29f7729 to
ba79691
Compare
Member
|
What's the use case for this? |
Contributor
Author
I have a function that returns https://docs.rs/syn/1.0.18/syn/struct.TypeParen.html EDIT, basically something along these lines: fn extract_tupled_types(attr: Attribute) -> Result<Vec<Type>> {
let ty: Type = syn::parse2(attr.tts)?;
Ok(match ty {
Type::Paren(paren) => vec![*paren.elem],
Type::Tuple(tuple) => tuple.elems.into_iter().collect(),
_ => vec![ty],
}) |
sfackler
reviewed
Apr 26, 2020
src/liballoc/boxed.rs
Outdated
Contributor
Author
There was a problem hiding this comment.
Ops, thanks. I just removed the From impl because it's insta-stable
Member
|
Seems plausible to me. Can you make a tracking issue and update the stability annotation? |
Contributor
Author
👍 Thanks! |
3 tasks
elichai
force-pushed
the
2020-04-boxed-slice
branch
from
ba79691 to
0228ca0
Compare
Member
|
@bors r+ rollup |
Collaborator
|
📌 Commit 0228ca0 has been approved by |
bors
added
S-waiting-on-bors
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 26, 2020
Rollup of 5 pull requests Successful merges: - rust-lang#71421 (Add a function to turn Box<T> into Box<[T]>) - rust-lang#71537 (Remove support for self-opening) - rust-lang#71551 (Minor refactoring around IndexVec usage in generator transformation) - rust-lang#71569 ([miri] Throw UB if target size and data size don't match) - rust-lang#71576 (check that `AsRef` and `AsMut` are inlined) Failed merges: - rust-lang#71558 (Cleanup and document `-Z tls-model` ) r? @ghost
shepmaster
reviewed
Jun 17, 2020
| /// | ||
| #[unstable(feature = "box_into_boxed_slice", issue = "71582")] | ||
| pub fn into_boxed_slice(boxed: Box<T>) -> Box<[T]> { | ||
| // *mut T and *mut [T; 1] have the same size and alignment |
Member
There was a problem hiding this comment.
This comment doesn't match the code. *mut T ≠ *mut [T]
Member
There was a problem hiding this comment.
That comment is justifying the cast to an array of length 1. The slice comes after.
Member
There was a problem hiding this comment.
What justifies the subsequent cast?
Member
There was a problem hiding this comment.
That's just unsizing, but we could leave that out and let the Box<[T; 1]> implicitly coerce unsized in the return.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
Hi,
I think this is very useful, as currently it's not possible in safe rust to do this without re-allocating.
an alternative implementation of the same function can be:
The only thing that makes me a little uncomfortable is this line :
from https://rust-lang.github.io/unsafe-code-guidelines/layout/arrays-and-slices.html
But then I see:
from https://rust-lang.github.io/unsafe-code-guidelines/layout/pointers.html#representation
So I do believe this is valid(FWIW it also passes in miri https://play.rust-lang.org/?gist=c002b99364ee6b29862aeb3565a91c19)