{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicglfwluidilgvwsfm2tg7yytcvwx3atvutsamfsfkkjv3u7o72bi",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mmlvguyzdsy2"
  },
  "path": "/t/include-racy-reads-in-rust-memory-model-with-maybeinvalid-t/24289#post_20",
  "publishedAt": "2026-05-24T10:17:20.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Adding _any_ new primitive operation to a memory model requires re-doing all proofs about the model. Memory models aren't \"additive\"; their correctness relies as much on the exact details of the existing operations as it does on the _absence_ of other operations.\n\nIIUC, the goal of this thread is to enable SeqLocks in well-defined Rust. The by far most promising avenue to achieve that is atomic bytewise memcpy. The alternatives you are proposing are a lot more complicated in terms of what would have to be done to ensure they are well-defined and sound.",
  "title": "Include racy reads in Rust memory model with `MaybeInvalid<T>`"
}