{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidj5ctdgxag6e2ohltiqtj46fnd7rheykeizwcshtoo2n2hnprudm",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhnloorqzfj2"
  },
  "path": "/t/idea-borrowck-transparent-function-calls/24103#post_20",
  "publishedAt": "2026-03-21T21:53:44.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "zirconium-n:\n\n> But here's the thing, partial borrowing (or we call them view types) absolutely won't come out in 3 years, it has much higher language semantic implications. TFC is a much smaller proposal, I can implement it myself in like 2 months. \"Wait for view types\" is basically equivalent to \"forget about this\" to me.\n\nYou could counter that with: if there is a half solution, the need for the full solution gets less and thus it will take even longer since there will be less resources for it. Also, once the full solution is stabilised, what do we do with the half solution? If it was stabilised we can't remove it. Would this idea still be useful to you as a perma-unstable feature that is removed once we get view types?",
  "title": "Idea: Borrowck Transparent Function Calls"
}