{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibhxkkk7br4sln36qer4dhddbsikpz67qkodjp3yv7rcw4g74mrg4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mk55nqs4h7l2"
  },
  "path": "/t/pre-rfc-a-tiny-internal-change-to-reverse-copy-from-slice-swap-with-slice/24189#post_4",
  "publishedAt": "2026-04-23T03:16:52.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I don't know if I'd say this is a _good_ way to think of it, but a slice reference is kind of a pointer/metadata pair (where the metadata is the length), so `as_mut_ptr` could be seen as exclusively borrowing the pointer part but not the metadata part, similar to what you can do with separate fields of tuples (or structs). It wouldn't have to _only_ be an optimization thing. (The special bit would then be that you're doing it using methods instead of direct field access, but at least that's instantaneous special behavior rather than ongoing, and something at least some people would like to support for arbitrary methods some day.)",
  "title": "[Pre-RFC] A tiny internal change to `reverse`, `copy_from_slice`, `swap_with_slice`"
}