-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Regression: could not convert tokens
in some macros
#17701
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
could not convert tokens
in some macroscould not convert tokens
in some macros
I started seeing this recently (in the last day or so) with the I'm seeing it in all usages of the macro in the Zed repo: |
Ugh our |
fix: Fix includes not working with expr fragment inputs Temporary workaround for #17701
#17706 should workaround this issue for now |
fix: Fix includes not working with expr fragment inputs Temporary workaround for rust-lang/rust-analyzer#17701
I'm still seeing this in 0.3.2053, even though the changelog says it includes the #17706 fix. I did a full uninstall-reinstall of the VS Code extension and created a fresh project (in case there was some cached state), but still the same error. (I also tried 0.3.2054, but that only changed the error to "Expected string literal.") An example that exhibits the error for me is https://github.com/itowlson/ra-macro-errors. The red line shows on the Environment: WSL (Ubuntu 22.04) Thanks! |
I am also still seeing this |
fix: Fix includes not working with expr fragment inputs Temporary workaround for rust-lang/rust-analyzer#17701
fix: Fix builtin includes rejecting raw string literals Fixes rust-lang/rust-analyzer#17701
fix: Fix builtin includes rejecting raw string literals Fixes rust-lang/rust-analyzer#17701
rust-analyzer version: v0.3.2045
rustc version: rustc 1.79.0 (129f3b996 2024-06-10)
editor or extension: VSCode
code snippet to reproduce:
Upstream issue: denoland/deno_core#844
The macro in question: https://github.com/denoland/deno_core/blob/85b40e5d47e568563957b031b5c3d4673226cc20/core/extensions.rs#L386
The text was updated successfully, but these errors were encountered: