{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigvkoausfxlijggd6h6kn5wm4t6e25mwdh4ujaws7oeackvjteoye",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhet4ye57dv2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093#post_13",
  "publishedAt": "2026-03-18T15:35:43.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Thanks, this is awesome. It's useful and clarifies something for me (I didn't know this before).\n\nMy understanding of what you said is that StableCrateId includes the unique id of a crate, which includes its origin, version, and what it depends on. Also, DefPath and its disambiguator(s) are already established mechanisms for establishing unique types in a crate.\n\nWould combining StableCrateId with DefPath make a practical basis for stable type identifiers? The one real question remaining is whether or not this can be made stable between compiler versions, as opposed to them being implementation details of rustc.",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}