{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiae5as6udbpczvz6ls4obvlyx3wl6nn6ye3so5jiewniazrsjv6rq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhrvqowm2yw2"
  },
  "path": "/t/idea-borrowck-transparent-function-calls/24103?page=2#post_21",
  "publishedAt": "2026-03-22T23:13:06.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I believe it would be. The reason is that currently, if I want the equivalent of some values being mutable and others not, or for that matter \"splitting the self-borrow\", the relevant values cannot be part of `Self` at all, and need to be passed in as separate arguments.\n\nWhile that works, it can be a lot of refactor work at times, depending on the context, and lacking automated refactoring tools, that all becomes manual work on the plate of the developer. In addition, it's also not the most discoverable solution. It is a mitigation strategy I only learned about after having > 5 years of Rust experience.",
  "title": "Idea: Borrowck Transparent Function Calls"
}