{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaa2ipu67bwua7adeyyirudbfcvkg52uz6ez4zrbzioyx4holxuum",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mlzpdr6mgar2"
  },
  "path": "/t/reducing-raw-pointer-footguns-preventing-reference-aliasing-violations-at-compile-time/24301?page=2#post_30",
  "publishedAt": "2026-05-17T05:00:41.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "robofinch:\n\n> When I make an `unsafe` concurrent data structure like a skiplist with lock-free reads, then forget relying on compile-time checks, forget relying on _only_ Miri; I’m going to do exhaustive `loom` tests.\n\nDo you have an example of this sort of code? I've been looking into \"what sort of features would safe Rust need to be able to allow it to replicate all/most unsafe Rust\" with a focus on avoiding race conditions in nontrivial cases, so I'd love to be able to see a really difficult example (because both the outcome of \"the safe Rust extensions I was thinking about are sufficient to make this work\", and \"this is impossible to do even with my extensions, because of X\" would be very useful results). Even an outcome of \"this can't be made safe, but at least it's possible to reduce the amount of testing required\" would be both interesting and useful.",
  "title": "Reducing Raw Pointer Footguns: Preventing Reference Aliasing Violations at Compile Time"
}