-
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
Most (all?) macros are unresolved #9101
Comments
The server logs hundreds of messages like
|
Which Rust version are you using? |
Seeing something similar although not quite:
Toolchain: Rust analyzer 4f63e79 (Merge #9097) FWIW I've seen the Happy to provide more debugging information. |
We don't really support Rust versions older than the current stable |
@jonas-schievink Ok, good to know. Feel to close this if you don't consider issues involving old stable to be bugs in rust-analyzer. |
For now, I'm adding a fallback to the legacy prelude in #9102, please test if that fixes your issue |
#9102 reduces my error log to:
So that's progress. :) |
Do names resolve correctly? The PR also silences the error |
#9102 fixes the issue for me. |
Bisected to f96c1a0 . This makes rust-analyzer basically unusable as even basic things from the prelude like
vec![]
andtodo!()
are unresolved.In case it matters, the code I'm working on is the latest origin/main of https://github.com/MaterializeInc/materialize .
The text was updated successfully, but these errors were encountered: