{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidqpsggynoz2esyo3l7g53dmo6t6jssnchscirljugxrqjud6qoo4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhdrjq6lsss2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093#post_8",
  "publishedAt": "2026-03-18T13:17:57.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "ParaDevOne:\n\n>   * **#3435 (export)** deals with how to export symbol information dynamically. It requires stable identifiers, but also does not define them.\n>   * **The proposal** presented in this document will provide the missing piece, which is an unambiguous, deterministic identifier for all types.\n>\n\n\nI think you misunderstood #3435, what is needs are identifiers based on the \"identity\" of a type such that if the type changes in some non-ABI compatible way then the identifier will change as well. Your proposal explicitly does not do this.",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}