-
Notifications
You must be signed in to change notification settings - Fork 1.7k
vec! - could not resolve macro $crate::__export::force_expr
#7349
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Cannot reproduce in linux, have you tried to create a new project and try again ? Any output in the Output Panel ? |
Me neither, and there's no |
@lnicola rustc nightly is change the implementation of |
That was with I should have mentioned I was using nightly rustc, yeah:
Using the following vscode settings: {
"rust-analyzer.trace.server": "verbose",
"rust-analyzer.trace.extension": true,
"rust-analyzer.updates.channel": "nightly",
} Language Server Trace
Client Output
|
Yes, I can reproduce it now in rustc nightly toolchain, I will take a look for that. |
Oh .. Seem like they start to use macro 2.0 for the vec macro :( |
cc #2248 |
I also have this bug on rust nightly with rust-analyzer nightly on macOS. |
…li-obk Turn alloc's force_expr macro into a regular macro_rules. This turns `alloc`'s `force_expr` macro into a regular `macro_rules`. Otherwise rust-analyzer doesn't understand `vec![]`. See rust-lang/rust-analyzer#7349 and rust-lang#81080 (comment) Edit: See rust-lang#81241 (comment) for a discussion of alternatives.
Fixed by rust-lang/rust#81241 |
Extension:
0.3.458-nightly
Server: rust-analyzer 5231f4b
VS Code:
Minimal case -
main.rs
Underlines
vec![1, 2, 3]
withTested with procedural macro and build script support both enabled/disabled.
Disabled all other extensions and commented out entire VS Code settings, still no dice.
Used to work but started breaking within the last couple days, I think.
The text was updated successfully, but these errors were encountered: