{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidkjdolpnftj3b6tlytatm5rdm7ia77axopesf7np5j4hafaot5ny",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mn5rfjo6zdp2"
  },
  "path": "/t/include-racy-reads-in-rust-memory-model-with-maybeinvalid-t/24289?page=2#post_35",
  "publishedAt": "2026-05-31T14:23:30.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "blog post"
  ],
  "textContent": "newpavlov:\n\n> [citation needed]\n\nThat's not how this works. You can't just assume something is sound and expect me to cite a refutation You have to argue why depending on future choices is sound.. The argument I laid out in my blog post _crucially_ depends on the story being expressible as actual Rust code. So if you want to make future-dependent choices, you'll need to develop an entirely different framework for justifying inline assembly blocks. I look forward to your blog post and correctness argument on that subject.",
  "title": "Include racy reads in Rust memory model with `MaybeInvalid<T>`"
}