{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiet4zfk4sjvxoko6pazp6tkdwtze3ywj47zj4fm4x2sy2cc3ox62q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mm7xt3t6d6p2"
  },
  "path": "/t/mutually-exclusive-traits/24337#post_4",
  "publishedAt": "2026-05-18T17:59:36.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "kpreid:\n\n> I don’t know if there are any plans to make negative impls usable to enable otherwise conflicting impls.\n\nAFAIK there's a general \"yes, that would be nice\" _wish_ for that to eventually be the case, but no concrete _plans_.\n\nFor example, I would like negative impls to replace the concept of fundamental traits, so we could do things like `impl !FnOnce for String` to solve some of the pattern-related reasons that certain traits are fundamental today.",
  "title": "Mutually exclusive traits"
}