-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rename Allocation::retag -> with_tags_and_extra #64503
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
@bors r+ rollup feel free to merge this with a miri-up for p=1 |
📌 Commit ac8ecbc9dc32aed661107bec30644130a5a326f4 has been approved by |
ac8ecbc
to
e8d858e
Compare
@bors r=oli-obk |
📌 Commit 686170e has been approved by |
@bors rollup- |
I think you meant... |
Not really, I just meant to undo the |
Oh, sorry about that then! I didn't think rollup- was a valid command. Now I have no idea how to undo what I did... |
@bors rollup=maybe |
rename Allocation::retag -> with_tags_and_extra This is more consistent with `Pointer::with_tag`. Also, "retag" is a [term from Stacked Borrows](https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md#retagging) with a [corresponding Machine hook](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/interpret/machine/trait.Machine.html#method.retag), and this function has nothing to do with that other use of the term. r? @oli-obk
@bors rollup- |
rustup for retag rename This is the Miri side of rust-lang/rust#64503. Do not force-push!
This is more consistent with
Pointer::with_tag
. Also, "retag" is a term from Stacked Borrows with a corresponding Machine hook, and this function has nothing to do with that other use of the term.r? @oli-obk