{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibw52rykxrlea6veuubsbtn6dznts3kgoayohj6rphdbgk2ten27m",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mmhxa3he5vw2"
  },
  "path": "/t/another-experiment-to-make-unsafe-rust-safer-preventing-ub-in-maybeuninit-with-compile-time-error/24352#post_8",
  "publishedAt": "2026-05-22T20:41:57.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "By the way, some big-picture advice, if you want it: in this thread and your previous one, you’ve thought up a type which makes some existing `unsafe` type harder to misuse. That’s good, but the part that’s missing, in both cases, is looking at it from the opposite direction: how powerful the new type is relative to existing _safe_ types. In order for a new idea in this area to be useful, it needs to be _both_ harder to misuse than existing `unsafe` options and more powerful (in some way) than existing safe options.",
  "title": "Another Experiment To Make Unsafe Rust Safer: Preventing UB In MaybeUninit With Compile Time Error"
}