{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigruqgiu6bkqhnriwec3xsauxd55cz27dznbg6jwxkz2zeynzoxdu",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mpk6b32yvue2"
  },
  "path": "/t/language-vision-regarding-safety-guarantees/24418?page=2#post_24",
  "publishedAt": "2026-06-30T23:06:01.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "ais523:\n\n> I'm not sure that there's any sensible way to cover this gap. (It almost seems as though the \"safety level\" or \"trust level\" should be some sort of generic parameter, but I can't think of a way to make that work.)\n\nI don't think there's actually a gap here, because if there is it's the same gap as \"well arbitrary safe code correctness is also relevant to soundness\", which in the limit means that everything needs to be unsafe, which isn't helpful",
  "title": "Language vision regarding safety guarantees"
}