{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiahzk2d2v32rqeae6caiop4yg4vqhxwyvwhiu6kxihidewkrhrqju",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mi7bavn6q2q2"
  },
  "path": "/t/introduce-a-way-to-construct-range-from-start-length/24073?page=2#post_41",
  "publishedAt": "2026-03-28T17:30:32.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I know that in general using inclusive ranges are slower than exclusive ranges, since the type needs to keep track of if it reached the end separately (in case the ending value is one that would overflow).\n\nHowever, I don't know if rustc can optimise this when the range is known at compile time to not overflow. Otherwise you really should be writing `'a'..'{'`, which is not ideal for human readers.",
  "title": "Introduce a way to construct Range from start + length"
}