{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicdogewebv3pov3a7jzpgkjplb63pxmma4nc4hlsc4cbrk4tzkwja",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhdyb35qll42"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093#post_14",
  "publishedAt": "2026-03-18T15:41:45.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Yes, I was incorrect about what I thought #3435 needed. My proposed solution addresses a different problem than what #3435 was originally intended for; specifically, stable type identification of a type across different compiler versions/builds, not detecting an ABI incompatible change. There are two different problems.\n\nIs there any existing work or discussion on stable type identification that is not tied directly to ABI compatibility?",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}