-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Add slice::{from_ptr_range, from_mut_ptr_range}
#89793
Conversation
r? @m-ou-se (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
4345b03
to
acccd0e
Compare
This comment has been minimized.
This comment has been minimized.
f4077e7
to
91e71cd
Compare
☔ The latest upstream changes (presumably #88540) made this pull request unmergeable. Please resolve the merge conflicts. |
8cc9609
to
acbaae7
Compare
This comment has been minimized.
This comment has been minimized.
acbaae7
to
5eee5e5
Compare
☔ The latest upstream changes (presumably #91433) made this pull request unmergeable. Please resolve the merge conflicts. |
@m-ou-se can you review this when you have the time, or should it be assigned to someone else? |
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.
Apologies.
This looks good to me.
There is just one issue that worries me: There have been (incomplete) plans for quite a while to replace Range
by two types: One that is Copy
, and one that is an iterator. Using Range
in signatures like this makes that change a little bit harder than it already is. Of course, the existing (and stable) .as_ptr_range()
already has this problem as it uses Range
as its return type. Still, I'm worried about making a potential change to Range
even harder by adding the functions in this PR.
That doesn't have to stand in the way of adding these as unstable. I have added this as an unresolved question to the tracking issue, so we can make sure to address it before stabilizing this.
If you can fix the merge conflict, this is ready to merge.
5eee5e5
to
a7c0290
Compare
Fixed @m-ou-se |
This comment has been minimized.
This comment has been minimized.
Can you rebase/squash the commits? Because now there's a commit named "update rust-analyzer submodule", which shouldn't be part of this PR. |
eb511d9
to
183e950
Compare
squashed @m-ou-se |
This comment has been minimized.
This comment has been minimized.
183e950
to
aac0281
Compare
@bors r+ rollup |
📌 Commit aac0281 has been approved by |
…askrgr Rollup of 5 pull requests Successful merges: - rust-lang#89793 (Add `slice::{from_ptr_range, from_mut_ptr_range} `) - rust-lang#92642 (Update search location from a relative path to absolute) - rust-lang#93389 (regression for issue 90847) - rust-lang#93413 (Fix broken link from rustdoc docs to ayu theme) - rust-lang#94365 (Fix MinGW target detection in raw-dylib) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Adds
slice::{from_ptr_range, from_mut_ptr_range}
as counterparts toslice::{as_ptr_range, as_mut_ptr_range}
.