{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibxo2ib4tzqjtbz2frrbwit7pth57gwzrvugz2q3lofajfaqydnpy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3milyebmit7f2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093?page=2#post_35",
  "publishedAt": "2026-04-02T18:02:23.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "The fact that the network layer uses serialization actually expands the use case you already acknowledged; it doesn't restrict it. Regarding plugins, not all of them require an ABI; those based on WASM, IPC, or explicit serialization do not need one. And the Bevy issue wasn’t closed because the problem went away: cart closed it because they settled for TypePath as a workaround, explicitly acknowledging that the language doesn’t provide the right tool for this.",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}