-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
ptr::invalid is not equivalent to a int2ptr cast #97482
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
r? @thomcc (rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
📌 Commit 852777e has been approved by |
ptr::invalid is not equivalent to a int2ptr cast I just realized I forgot to update these docs when adding `from_exposed_addr`. Right now the docs say `invalid` and `from_exposed_addr` are both equivalent to a cast, and that is clearly not what we want. Cc `@Gankra`
…laumeGomez Rollup of 5 pull requests Successful merges: - rust-lang#96950 (Add regression test for rust-lang#96395) - rust-lang#97028 (Add support for embedding pretty printers via `#[debugger_visualizer]` attribute) - rust-lang#97478 (Remove FIXME on `ExtCtxt::fn_decl()`) - rust-lang#97479 (Make some tests check-pass) - rust-lang#97482 (ptr::invalid is not equivalent to a int2ptr cast) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
I just realized I forgot to update these docs when adding
from_exposed_addr
.Right now the docs say
invalid
andfrom_exposed_addr
are both equivalent to a cast, and that is clearly not what we want (and is also not the case any more in terms of implementation since #97219).Cc @Gankra