-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Goto definition - all shown twice #6414
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
@neilyoung do you have another Rust extension enabled? Please disable the vscode-rust extension when using rust-analyzer. |
I can't reproduce this, but it might also be caused by the |
Hmm. I was now away from Rust for four weeks. The November edition of VSCode now complained about "5 crashes in a row with rust-analyzer". I deinstalled and installed again. Doesn't work anymore...
|
Yeah, you'll need 1.52 due to an incompatibility (#6979). |
Oh. Then I would rater wait for your fix. I never downgraded VSCode so far... |
Oh, 1.52 is the November release (from December). Hmm.. |
I'm having 1.52.1 on macOS |
Which extension version are you using? The one released today? |
0.2.424 |
Is that the latest you are referring too? |
Yes, it's the one from today. I'm not sure why you're getting that error. |
@neilyoung triage ping, does it work with the newest weekly release? |
@flodiebold Sorry, right now I can't even tell. If you mean the "Initial parameter" issue, then this was fixed as commented in #6983. For the initial issue posted here I'm trying to get an answer, but my VSCode surprised me with the message, that I have to install rust-analyzer-server. And this fails since two days now already (I recently upgraded to Big Sur, not sure if this matters). |
Right now it finished. It seems that my "double whopper" is also gone. :) Can be closed |
There are implementations of Default, Debug and Clone derived for that type. The Serialize and Deserialize derives couldn't be expanded. Likely because proc-macro support isn't enabled by you. |
Ah. Thanks. Can be closed. How could I enable "pro-macro" support? |
You can enable proc-macro support using {
"rust-analyzer.cargo.loadOutDirsFromCheck": true,
"rust-analyzer.procMacro.enable": true,
} |
Thanks! EDIT: One observation: The latest version of RA is all the time indexing my project after each start. I never noticed that, at least not, if I didn't make any change to my Cargo.toml. Is that "normal"? EDIT2: The settings above don't change my inability to follow the derivates. |
Yes, it is normal for it to start indexing every time it is started. No parts of the analysis are stored in between runs. |
Let me say first: I love your rust-analyzer (even though it causes pretty heavy load to my old MBP).
I have a question regarding "CMD_CLICK" to a symbol, which is AFAIK "show references".
If your plugin is disabled, this is shown while hovering over a symbol...
...and once I CMD_CLICK on the symbol the appropriate source file is opened and the cursor is positioned to the place where the symbol is defined.
Now, with your extension installed, the display changes a bit (it is annotated):
...and CMD_CLICK opens a popup-window, showing twice the same reference:
I suspect, this is because the symbol is shown twice in the hovering information. It is not such a big thing, but a bit annoying, if you just expect one place to be shown.
Regards
The text was updated successfully, but these errors were encountered: