-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rename rustc_middle::Ty::is_unsafe_ptr to is_raw_ptr #135994
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
Conversation
Could not assign reviewer from: |
Some changes occurred to the CTFE machinery cc @rust-lang/wg-const-eval Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred to the CTFE / Miri interpreter cc @rust-lang/miri Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
This comment has been minimized.
This comment has been minimized.
r? Noratrieb testing something |
Please choose another assignee. (see documentation) |
r? oli-obk more testing |
Could not assign reviewer from: |
Clippy also has a lint with |
Please choose another assignee. (see documentation) |
You have insufficient capacity to be assigned the pull request at this time. PR assignment has been reverted. Please choose another assignee or increase your assignment limit. (see documentation) |
r? oli-obk |
I believe you are speaking on |
Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 This PR changes Stable MIR cc @oli-obk, @celinval, @ouz-a rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
This comment has been minimized.
This comment has been minimized.
The Miri subtree was changed cc @rust-lang/miri |
Ah I see, makes sense. |
apparent merge conflicts? @bors r- |
even with the master branch I mean. also |
6afd0c9
to
b4abf2f
Compare
This should work now :) Sorry for the confusion, the other patch landed first and broke this one. |
☔ The latest upstream changes (presumably #136751) made this pull request unmergeable. Please resolve the merge conflicts. |
The wording unsafe pointer is less common and not mentioned in a lot of places, instead this is usually called a "raw pointer". For the sake of uniformity, we rename this method. This came up during the review of rust-lang#134424.
b4abf2f
to
0c7d5e2
Compare
Friendly ping on this change :) Should be ready to merge once again! |
@workingjubilee @oli-obk Is there anything that blocks this from landing? I saw that Jubilee was r-'ing this patch but I assume that is because of the merge conflict that's now resolved, or do I miss something? :) |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6dce9f8): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 2.4%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 790.496s -> 788.472s (-0.26%) |
The wording unsafe pointer is less common and not mentioned in a lot of places, instead this is usually called a "raw pointer". For the sake of uniformity, we rename this method.
This came up during the review of
#134424.
r? @Noratrieb