-
Notifications
You must be signed in to change notification settings - Fork 1.8k
proc macro returned error: Cannot perform expansion for Deserialize: error Unknown #6686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Downgrading the extension on my Mac to the latest stable version (v0.2.400) resolves the issue. Weirdly, on one Linux box, I needed to downgrade to v0.2.392; I still see rust-analyzer crashing on v0.2.400. Attached are server trace logs, and here's the panic message, from the "output" tab:
|
This kind of error is usually caused by an incompatibility between the libproc_macro version of rustc and rust-analyzer. If this is the case, the fix will have to wait until the current rustc nightly hits stable. |
This is not a regression, the |
I'm not seeing a diagnostic for this error but hover shows that it fails.
|
Triage: can't reproduce. @tomjakubowski do you see any errors now ? |
Seems fixed, probably by #7047. |
Uh oh!
There was an error while loading. Please reload this page.
It seems there's been a recent regression in derive proc macros on the nightly channel. I'm on v0.3.367-nightly
and see red squigglies on these entire structs (along with any comments), and a corresponding proc macro error.
Sometimes the error message instead says "Empty result", or "Server closed".
Unsure when this might have been introduced, but I have been on the nightly channel for some time, and wasn't seeing this last week Wednesday in a project that uses proc macros, but do see it today.
I have
"rust-analyzer.procMacro.enable
andrust-analyzer.cargo.loadOutDirsFromCheck
both set to true.I've attached the testcase I used for the screenshots: testcase.tar.gz
The text was updated successfully, but these errors were encountered: