ptr: introduce len() method on raw slices #71082
Merged
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 @shepmaster (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
|
cc @rust-lang/wg-const-eval |
|
One question I have is whether we can put this onto slices directly, such that |
|
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 |
|
Cc #60639 |
|
This would also be covered by the more general rust-lang/rfcs#2580. (Please comment there in support if you’d like!) |
I did think of this solution and actually tried it first, but as I understand it the function would have to be put in a trait then (I can't add an |
This is possible but requires significantly more work, including on the compiler side: #60639 (comment) |
Looking into it. |
|
I have pushed an update which implements len() as a method, also introducing the lang items needed for #60639. For now, I've left the old version in the PR as well - I'll remove those commits if we decide to go for the method. |
|
This is awesome! The implementation lgtm, but the library method addition should probably be signed off by a libs team member. r? @SimonSapin or someone else from @rust-lang/libs
Even so, this new function is imo reasonable to have even if at some point its body is implemented via that rfc.
My personal preference is that we should go with the inherent method approach not have a free function at all. |
|
I agree that since we can have the inherent method, there's no need for the non-inherent method: the inherent method is strictly better. |
Centril
added
T-lang
Add lang items for methods on raw slices.
It is already possible to extract the pointer part of a raw slice by a simple cast, but retrieving the length is not possible without relying on the representation of the raw slice when it is not valid to convert the raw slice into a slice reference (i.e. the pointer is null or unaligned). Introduce a len() method on raw slices to add this missing feature.
neocturne
changed the title
neocturne
force-pushed
the
ptr_slice_len
branch
from
258d1d7 to
2a29f8f
Compare
Right, I never intended to have both versions included, I just wanted to give more people a chance to give feedback on the original proposal before removing it. What are the next steps here? Do I open tracking issues for the unstable features, or should I wait for a review? |
|
@NeoRaider Yes, now that there’s rough consensus for having something like this at all please file a tracking issue and add its number to the @Centril Why did you add needs-fcp and relnotes labels? This PR only adds unstable APIs, I’d expect to see those labels in the stabilization PR. |
|
@SimonSapin ah woops, my mistake! |
7 tasks
jonas-schievink
removed
needs-fcp
|
@bors r=oli-obk,SimonSapin |
|
📌 Commit dfd6844 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 15, 2020
Rollup of 8 pull requests Successful merges: - rust-lang#70657 (Allow `try`-blocks in places where an open delim is expected) - rust-lang#70947 (tighten CTFE safety net for accesses to globals) - rust-lang#70949 (simplify `vec!` macro) - rust-lang#71002 (fix target & runtool args order) - rust-lang#71082 (ptr: introduce len() method on raw slices) - rust-lang#71128 (Remove unused single_step flag) - rust-lang#71133 (Tighten time complexity on the doc of sort_by_key) - rust-lang#71135 (Update books) Failed merges: r? @ghost
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.
It is already possible to extract the pointer part of a raw slice by a
simple cast, but retrieving the length is not possible without relying
on the representation of the raw slice when it is not valid to convert
the raw slice into a slice reference (i.e. the pointer is null or
unaligned).
Introduce a new function ptr::slice_len() to add this missing feature.Introduce a len() method on raw slices to add this missing feature.