{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibgaryvkngojsx3dcmj7jwguuk7zdjaalgyo3ui3mdhym322fvsxe",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mo7cc2n3xns2"
  },
  "path": "/t/the-hashtable-problem-a-litmus-test-for-external-impl-proposals/24396#post_12",
  "publishedAt": "2026-06-13T20:46:45.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "rust-rfcs/text/3634-scoped-impl-trait-for-type.md at 251e4c443757ebe7c079a8a3627e32f9b79d4d0e · Tamschi/rust-rfcs · GitHub"
  ],
  "textContent": "It's a good pattern for e.g. ordered containers I think, but it wouldn't solve the newtype pain points that external trait impls would cover: rust-rfcs/text/3634-scoped-impl-trait-for-type.md at 251e4c443757ebe7c079a8a3627e32f9b79d4d0e · Tamschi/rust-rfcs · GitHub\n\nImplementing it for everything that takes bounded generics also seems very noisy to me in terms of API surface.",
  "title": "The Hashtable Problem: A Litmus Test for External Impl Proposals"
}