{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibcvwhmjn2qedg6pbwzkzphg6ml6skfgerwbbtpjrcz4wkjnnhg2i",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mo622lxxxba2"
  },
  "path": "/t/the-hashtable-problem-a-litmus-test-for-external-impl-proposals/24396#post_6",
  "publishedAt": "2026-06-13T09:32:08.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "jrose:\n\n> Therefore \"the Hash implementation is part of the type that depends on Hash\" is _not_ a solution for the HashMap in std.\n\nWithout further additions, at least. It's _afaict_ okay as long as the impl identity constraint is enforced for any function calls where both implementing and depending type appear in the signature bounds-linked (even indirectly, so basically any case where those types are linked by relevant type parameter bounds).",
  "title": "The Hashtable Problem: A Litmus Test for External Impl Proposals"
}