{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicpj7ioywkivfzqdb3glvx4c7yiygwvytcawypbct4lfqvo5c6ghy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mh5a5jnn4322"
  },
  "path": "/t/dereferenceable-zero/23991?page=7#post_135",
  "publishedAt": "2026-03-15T19:42:41.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "@T"
  ],
  "textContent": "H4n_uL:\n\n> New-edition's `Option<@T>` is always 1-word-wide and `Option<&T>` is always 2-words-wide.\n\nYou need to stop trying to jump all the way to \"my use case is centered\", rather than taking incremental steps.\n\nWe're reasonably likely to add a function or two to help here.\n\nWe _might_ consider adding a library type, if there's enough demand and it becomes popular in the ecosystem.\n\nWe're extremely unlikely to add a new language built-in type.\n\nThere's no chance of that type ending up with a sigil; those are rare and valuable and get used for pervasive language features.\n\nThe idea of this feature being seen as so pervasive that it should become the _default type of reference_? Never. Zero chance. You really, really need to step back and approach this with a mindset of \"how can my niche use case be served a bit better\", rather than your current approach of \"why does Rust not pervasively revolve around my use case\".",
  "title": "Dereferenceable Zero"
}