{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicmblbwqq4n6y2itsyvghtrkg2b22yryaxhhkeq3mg7olrcjpnwoa",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mo622h4ab5f2"
  },
  "path": "/t/the-hashtable-problem-a-litmus-test-for-external-impl-proposals/24396#post_7",
  "publishedAt": "2026-06-13T09:36:34.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "benschulz:\n\n> This is only true for proposals that intend to allow overlapping implementations.\n\nRight. The main problem there is that disallowing them would make most added trait implementations a breaking change for any library crates.\n\nThis would not be (much of) an issue for executable-only crates, which would already cover a lot of ground in practice. There may be some ecosystem tradeoffs in terms of fewer stand-alone binaries being made also usable as libraries.",
  "title": "The Hashtable Problem: A Litmus Test for External Impl Proposals"
}