{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihc5qidjtpojbudbda5a2wnq2jb7ikaagzelwbwsczrjtumapvipe",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhi6k6i4bf72"
  },
  "path": "/t/idea-borrowck-transparent-function-calls/24103#post_6",
  "publishedAt": "2026-03-19T18:19:27.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "Private lifetime inference",
    "language design"
  ],
  "textContent": "I think the same thing about this as when essentially the same thing came up 2 days ago\n\nPrivate lifetime inference language design\n\n> TBH, getting lifetime bounds right is rarely the noisy part. I think it'd be entirely fine to solve that part like we solve -> _: with a structured suggestion inferred from the body. Then I agree with the mention of a macro fn: then it could potentially even just be macro fn find_best(primary, fallback) { if primary.is_valid() { &primary.summary } else { &fallback.summary } } where not only do I not need to put in the lifetimes but I can even leave off the types and have it just happen i…",
  "title": "Idea: Borrowck Transparent Function Calls"
}