{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigu67kvbi6q4d3vvytchozmm67vmpmawfiqgo3nzajp4z55zfvrym",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgzny2vj2yx2"
  },
  "path": "/t/could-borrow-checking-with-origins-unblock-sound-specialization/24079#post_5",
  "publishedAt": "2026-03-14T14:40:32.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "robofinch:\n\n> we further don't want to allow specialization on lifetimes at all.\n\nBut is this really the case? Specializing on `'static` seems like a perfectly valid use case. `'static` is not an origin computed by the borrow checker, it's a property of the data itself. No borrow checker upgrade will change whether a string literal or an owned type is `'static`. `T: 'static` is already a bound the solver understands.",
  "title": "Could borrow checking with origins unblock sound specialization"
}