{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig3jakvcq7hpljkdjl3yrfmcjvfdyev4gnekndlfu4gthfd3m46xy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkqlz2sy5ny2"
  },
  "path": "/t/sized-or-sizeable-str-e-g-str-const-n-usize/24213#post_7",
  "publishedAt": "2026-04-30T21:28:52.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "CAD97:\n\n> This method is fully `const` as of Rust 1.88 (for `<[_]>::as_chunks`). …\n>\n> Note that the `Option::unwrap` occurs _at`const` time_ due to the `const` block, so there is guaranteed no runtime overhead.\n\nThis is fascinating! Like the last time you helped me (which inspired my new `StringletBase` layout and workaround module) I’ll let this settle and see where I can take it. Thank you!\n\nSame thing though about macros as I replied to kpreid. And it would need two variants as the `const {}` one can’t handle dynamic data. I guess there must be reasons why `const fn`s are not simply always called at compile time. But it just seems so annoying – and counter-intuitive that the same keyword means different things.",
  "title": "Sized (or Sizeable) str, e.g. str<const N: usize>"
}