{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigdhbwg2nebncq7rptpfrirmy6qhdbggjo62qrtuxgi6lzrqlfq7e",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mn4wlfq6hfn2"
  },
  "path": "/t/parser-error-recovery-in-syn-for-better-ide-support-with-proc-macros/24362#post_9",
  "publishedAt": "2026-05-31T05:10:11.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "kpreid:\n\n> For attribute macros and derive macros, if the macro is getting called at all, you know that `rustc` thinks that the item _is_ valid syntax\n\nThis isn't an issue of rustc only calling proc-macros with valid inputs, but of rust-analyzer calling a macro with input that doesn't parse because you haven't finished writing the input code and are trying to get code completions.",
  "title": "Parser error recovery in `syn` for better IDE support with proc-macros"
}