{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifnzwxwqzgta2rngl6wyrzpksnj2halv32dttli7o3xi2v2ui3ej4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhdybjqffls2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093#post_11",
  "publishedAt": "2026-03-18T15:20:28.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I hadn't thought of that before and you are right. Hygienic macros create different objects that have the same path but are stored as different objects in the compiler.\n\nFor the time being, I have no definitive answer. In this case, would the existing hygiene information that the compiler tracks internally be enough to determine which is which in the hash? Or would a completely different method be needed?",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}