{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibsutfd6h4ug67n3avhnihdmdqzmj5wuuoaibkwvfss4mxtqkixmi",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhh4yz6y7qd2"
  },
  "path": "/t/idea-borrowck-transparent-function-calls/24103#post_3",
  "publishedAt": "2026-03-19T12:06:39.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "josh:\n\n> However, you're talking about non-public methods, and a mechanism that doesn't cross crate boundaries. For _that_ , the idea of a more automatic, less explicitly declared mechanism seems potentially reasonable. At the very least, it's worth considering.\n\nI disagree: it is a strength of rust that the function signature is the border of reasoning (in both directions). It helps bound the amount of work the compiler has to do, which helps compilation time. It also helps bound the amount of things a human has to keep in their head. Finally it helps with compile errors, keeping the error near the issue (C++ templates is an example of where this doesn't happen and the errors are awful).\n\nThat is a strength I would hate to loose. I want to see a solution to this issue, but it need to be an explicit solution, not an implicit one.",
  "title": "Idea: Borrowck Transparent Function Calls"
}