-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ERROR synthetic syntax
warning on any interaction with the editor
#19456
Comments
I'm not able to reproduce this, but I think those error come up from time to time. Just to be sure, do you get the docs when hovering on |
Ah, never mind, I can reproduce it on nightly. |
That message means we tried to emit a diagnostic for some desugared thing, something we shouldn't be doing. I can confirm that my logs are also apparently spammed with this message so we either changed some desugaring recently or when a specific diagnostic gets reported. Though I don't see any such relevant changes |
nightly-2025-03-22 works fine, nightly-2025-03-23 fails. |
Ah right, rust-lang/rust#136932 got merged so we need to adjust our lowering |
Still seems to be an issue |
rust-analyzer version: rust-analyzer version: 0.3.2353-standalone (37acea8 2025-03-23)
rustc version: rustc 1.87.0-nightly (f8c27dfe1 2025-03-24)
editor or extension: VSCode
relevant settings: i dont know
code snippet to reproduce:
minimal:
other examples:
any macro that calls format_args with an argument that can be formatted, will cause this "warning". the warning is in the OUTPUT section of the editor, under Rust Analyzer Language Server from the dropdown:
It will produce as many
ERROR synthetic syntax
messages as there are calls toformat_args!
in the source code (whether direct, or indirect, as shown above).I am pretty much sure this can't be reproduced, otherwise it would be recognized immediately. This doesn't cause any issue per se, but it is still annoying to not be able to see Rust Analyzer Language Server output because of this error.
It is also a very cryptic error message with no payload attached. Why is it like this?
The text was updated successfully, but these errors were encountered: