{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiewwsoz327tvtctfwx66k65cpcdutvvqtov4nwpt4iknosdtd6hui",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mhazzjmjfkq2"
  },
  "path": "/t/private-lifetime-inference/24088#post_9",
  "publishedAt": "2026-03-17T06:18:22.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "RFC: macro functions",
    "language design"
  ],
  "textContent": "I just want to bring this up as a restricted version of this proposal.\n\nRFC: macro functions language design\n\n> (I unfortunately don't have the bandwidth to actually put this through a full RFC for language inclusion, but this is a legitimate Request For Comments and proposal for improving the capability of Rust. This was written in one afternoon/evening on my smartphone; please forgive any formatting/grammar/procedural issues. A few sections have todos left to mark where I think detail is probably missing; please feel free to ask clarifying questions even/especially if they ask about the todo areas, as I…\n\nredradist:\n\n>   * Any technical blockers I'm missing?\n>\n\n\nThe main problem is circular dependency. You may need item `foo`'s definition to infer `bar`'s definition and vice versa at the same time. This will results a complex constrain solving, and that may not have an unique inference result.",
  "title": "Private lifetime inference"
}