{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih3gfjzdxvlafu34j7mzms6feua2rajbngg3fdy7pnjd2ezud6rge",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mk4qaefry6k2"
  },
  "path": "/t/pre-rfc-a-tiny-internal-change-to-reverse-copy-from-slice-swap-with-slice/24189#post_3",
  "publishedAt": "2026-04-22T23:27:23.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "> What's your plan to have a test for it to keep it from regressing?\n\nI think a comment explaining why those functions would be written that way should be enough to dissuade Rust maintainers from rewriting it without a stronger reason.\n\n> But at a broader level, note that `.len()` _is_ special. (...)\n\nAs far as I understand, these special cases are motivated by performance, or are there any that affect the functional behavior of `.len()`?\n\nI can recognize that what I'm proposing is a hard sell. Even if my proposal doesn't win, what I'm hoping to get out of this discussion is also a clearer understanding of what makes `self.len()` special in this context, if it is indeed special.",
  "title": "[Pre-RFC] A tiny internal change to `reverse`, `copy_from_slice`, `swap_with_slice`"
}