{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib427g2zhuluci5fh75d72bstlyw6vzeiif7yuiogmzjbtxpl2kpy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mj4jhasm6j22"
  },
  "path": "/t/pre-pre-rfc-allow-exclusion-of-trait-methods-for-certain-unsatisfiable-where-bounds/24160#post_6",
  "publishedAt": "2026-04-09T21:50:39.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "steffahn:\n\n> You might be interested to learn that actually one _can_ add the bound: For some reason, `rustc` doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked lifetime to it.\n\nThis is, I believe, an accidental stabilisation; the feature to allow trivial bounds is unstable (see the tracking issue linked earlier) but you can opt-in to it on stable Rust by adding a pointless higher-ranked lifetime, and lots of people seem to have figured that out (and even the people who don't figure it out on their own may see the \"see issue #48214\" in the error message, and the issue in question discusses the workaround).\n\nIt's unclear what to do about this; trivial bounds are already intended to be added to Rust at some point in the future, and although they're meant to be unstable at the time being (and posibly have bugs), there is a trivial workaround to make use of them anyway, so lots of people are. The only real way to resolve the situation would be to stabilise the feature, but I can imagine that that might be undesirable for a feature that might not be fully working/tested yet…",
  "title": "[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds"
}