{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaijswrcnykfrbloond4swqzahebbrmzy5m4niwj7btpideaayony",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3milyfgpwbzw2"
  },
  "path": "/t/stable-type-identifiers-a-missing-piece-for-crabi-and-export/24093?page=2#post_30",
  "publishedAt": "2026-04-02T11:12:24.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "ParaDevOne:\n\n> there is any prior work on stable type identification that isn’t directly tied to ABI compatibility.\n\nThen maybe I'm misunderstanding your goal:\n\nParaDevOne:\n\n> The use of stable type signatures is critical to having Rust-to-Rust dynamic linkage, as the absence of stable type information means that any dynamic linkage would require unsafe FFI in Rust\n\nHow do you reach that goal without tying such identifiers to the ABI? Your proposal as is doesn't reach the goal because it doesn't protect against UB from a mismatched ABI, so it must also be `unsafe`.",
  "title": "Stable type identifiers: a missing piece for crABI and export"
}