{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvr3plsxuxjv27p65tyzojruvvrfathk3xmsxlo3saxjc76ieyta",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mikq3hy636x2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093?page=2#post_33",
  "publishedAt": "2026-04-02T15:01:42.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "SkiFire13:\n\n> What problem are you trying to solve? What code, program, or system are you trying to write that you can't because you're missing this feature? And how would this feature solve it?\n\nThere is already a specific use case: Bevy issue #32, opened in 2020. The problem is that `TypeId` is not stable across binaries, making it unsuitable for serialization, networking, or plugin systems. The workaround has been `type_name` or `TypePath`; which the author himself described as sufficient for scenes and networking, but implemented manually at the library level, not provided by the language. That is exactly the drawback I’m describing: stable type identification independent of the ABI, with a real-world use case that a major Rust project has been patching for four years without a proper solution.",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}