{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig3tyixh45c27xhua32yqtg6ohmz6zuf5gztm64gyeglbuka3nsfu",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mm2dhdb6aot2"
  },
  "path": "/t/reducing-raw-pointer-footguns-preventing-reference-aliasing-violations-at-compile-time/24301?page=2#post_36",
  "publishedAt": "2026-05-17T10:54:57.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "fuji-184:\n\n> Maybe the safest usage of it is the Clippy check command to only give messages not edit\n\nOh, yeah, absolutely. I use neither `cargo clippy --fix` (I think that's the command?) nor even `cargo fmt` (I may agree with the linter, but I disagree with the formatter).\n\nPlus, the _immediate_ /direct problem found by `clippy` may be a symptom of the actual problem. Applying patchwork fixes to the direct problems won't actually fix the code in those cases, no matter how correct those patchwork fixes may or may not be.\n\nfuji-184:\n\n> Anyway, do you have any technical feedback? For example, what kinds of code would not work with this guard?\n\nI think there's large enough escape hatches that anything _could_ work with the guard, but maybe not _well_. Either way... I probably know the aliasing rules well enough that I'm not the target audience to begin with.",
  "title": "Reducing Raw Pointer Footguns: Preventing Reference Aliasing Violations at Compile Time"
}