-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Possible regression of the language server resulting in a panic #17986
Comments
Oh no, this is panicking within the proc-macro server (might be time for us to try backporting a fix to beta for the first time 🎉) |
That macro invocation is for some reason creating |
We seem to be losing the quotation marks |
fix: Fix TokenStream::to_string implementation dropping quotation marks Fixes #17986 We might wanna consider backporting this to beta if that's simple enough to do
…, r=Veykril fix: Fix TokenStream::to_string implementation dropping quotation marks Fixes rust-lang/rust-analyzer#17986 We might wanna consider backporting this to beta if that's simple enough to do
rust-analyzer version: rust-analyzer version: 0.3.2089-standalone (0f7f68d 2024-08-27)
rustc version: rustc 1.82.0-nightly (6de928dce 2024-08-18), though the error is there with stable too
editor or extension: VSCode
repository link (if public, optional): vrurg/fieldx
code snippet to reproduce: https://github.com/vrurg/fieldx
Straight to the output of the language server:
The problem pops up when the
enum_dispatch
crate is used in a proc_macro crate. For example, the entire trait is permanently marked as erroneous.The problem looks like a regression to me as it hadn't been observed until some moment in time a month or two ago.
The text was updated successfully, but these errors were encountered: