{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifitowr67szvwf6bx5eiqoz7fyxleljgudhfleycqdjkl4cx74mnq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgkqicc6tik2"
  },
  "path": "/t/idea-pre-rfc-null-free-pointer-and-zeroable-reference/23991?page=6#post_111",
  "publishedAt": "2026-03-08T09:46:59.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "H4n_uL:\n\n> As noted above, this has already led to a soundness issue.\n\nThe \"soundness issue\" is that I'm using a dummy implementation for the new `core::ptr` functions I proposed. You could replace it by `read_volatile` today and mark the calling functions non-const. Then it will work and be sound today, just a bit slower.\n\nH4n_uL:\n\n> this may seem like an excessive solution at first glance\n\nIt is an excessive solution, since the benefits are so small. The use-cases you address are extremely rare, and already have usable workarounds today. And in the end, Rust doesn't have to be usable for every single application.\n\nYou can of course continue to argue for complex solutions which have absolutely no chance of being accepted. Or you could try to find low impact solutions (like the handful of functions I proposed) which help your use-cases without impacting Rust at large. Those might actually have a chance of happening.",
  "title": "Idea / Pre-RFC: Null-free pointer and Zeroable reference"
}