-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Implement ptr_cast_array
#144515
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
base: master
Are you sure you want to change the base?
Implement ptr_cast_array
#144515
Conversation
@@ -330,7 +330,7 @@ impl<T> [T] { | |||
} else { | |||
// SAFETY: We explicitly check for the correct number of elements, | |||
// and do not let the reference outlive the slice. | |||
Some(unsafe { &*(self.as_ptr().cast::<[T; N]>()) }) | |||
Some(unsafe { &*(self.as_ptr().cast_array()) }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed this in the libs-api thread before it was accepted but didn't want to be off-topic.
I was wondering how many uses of unsafe ptr casts are really just working around lack of const casting traits.
I think all of chunk methods could also be a fixme(const-hack)
for TryFrom
not being const before the const trait initiative. So the unsafe could also be removed here eventually.
I thought the other cast_array uses were more motivating outside of this module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, there's a bunch of different ways this could be done. Certainly there's also options like self.as_chunks().0.first()
that would work for this function.
I don't think these chunk methods would be TryFrom
, though, because the &[T; N] as TryFrom<&[T]>
intentionally requires an exact length match. (That's aligned with the general guidance that "from" stuff gives the "same" thing, and having them be eq
needs the lengths to be the same.)
But yeah, .get(..N)?.as_array()
(https://doc.rust-lang.org/nightly/std/primitive.slice.html#method.as_array) would be an option if get
worked in const. (That's still two checks in the MIR, though, so dunno if it's better that way or not.)
EDIT: Oh, wait, not, the as_chunks
version doesn't work because that panics for N == 0
. But yes, lots of options. Even split_at_checked(N)?.0.as_array()
, I suppose, which doesn't need to wait for const-trait.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of TryInto
(unless that has the same issues and I'm just mistaken/misremembering). But as you said, now we have a lot of other options.
ACP: rust-lang/libs-team#602
Tracking Issue: #144514