{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihmratqcmhxjga33b773y6vqggdiyg3zi7kxhkab6g3dbvcccssga",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mm2xlmtgzhr2"
  },
  "path": "/t/reducing-raw-pointer-footguns-preventing-reference-aliasing-violations-at-compile-time/24301?page=2#post_37",
  "publishedAt": "2026-05-17T16:22:17.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I think this word is popular in the Rust community\n\n\"Even the best programmers can make mistakes\"\n\nThat acknowledges we are just human. That is also the reason why raw pointers are avoided as much as possible\n\nBut regardless of what you think about it, I need some clear technical feedback, which is specific and not generic like \"I think there are many\", what are those \"many\" things? because I don't know what they are\n\nWhat I expect is : \"Oh this lacks A because of reason B\", \"Oh, if this faces case C, it will cause D\", etc. The message is clear about what it means",
  "title": "Reducing Raw Pointer Footguns: Preventing Reference Aliasing Violations at Compile Time"
}