{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibujnzamgaqvokgbkns7zrqxbv4nupvrd2y6kchysf3oty7q6tfpm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mh7kzqxdisa2"
  },
  "path": "/t/maybeinvalid-t-separate-concepts-of-uninitialized-memory-and-invalid-values/24087#post_2",
  "publishedAt": "2026-03-16T19:46:24.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "github.com/rust-lang/rfcs",
    "MaybeDangling (#3336)",
    "RalfJung",
    "+268 -0",
    "…",
    "Rendered",
    "@rust-lang"
  ],
  "textContent": "Sounds like you might be interested in\n\ngithub.com/rust-lang/rfcs\n\n####  MaybeDangling (#3336)\n\n`master` ← `RalfJung:maybe-dangling`\n\nopened 02:59PM - 29 Oct 22 UTC\n\n RalfJung \n\n +268 -0 \n\nDeclare that references and `Box` inside a new `MaybeDangling` type do not need …to satisfy any memory-dependent validity properties (such as `dereferenceable` and `noalias`). Rendered Thanks to @rust-lang/wg-unsafe-code-guidelines for a lot of helpful feedback :) Tracking: - https://github.com/rust-lang/rust/issues/118166",
  "title": "`MaybeInvalid<T>` - separate concepts of uninitialized memory and invalid values"
}