{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieyntccxqjw4pqnh3z42i4ml6lfxcef6p45crgmxamtwc5s5of2de",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3melntldrzd72"
  },
  "path": "/t/conditions-for-unsafe-code-to-rely-on-correctness/23995#post_14",
  "publishedAt": "2026-02-11T13:59:24.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "the nomicon"
  ],
  "textContent": "As far as I can tell, the nearest \"official\" statement is in the nomicon:\n\n> The design of the safe/unsafe split means that there is an asymmetric trust relationship between Safe and Unsafe Rust. Safe Rust inherently has to trust that any Unsafe Rust it touches has been written correctly. On the other hand, Unsafe Rust cannot trust Safe Rust without care.",
  "title": "Conditions for unsafe code to rely on correctness"
}