unresolved import for proc-macro generated identifier

[ndmitchell]

In our project we have a bunch of types generated from proc-macros. Recently (probably since #6016) all such imports are flagged as unresolved import. That seems to be an expected consequence. Is there any way to disable such errors, as it makes it vastly harder to see real errors from Rust Analyzer.

[bjorn3]

"rust-analyzer.diagnostics.disabled": ["unresolved-import"] should work I think.

[bjorn3]

Also you can enable proc-macro support using

{
    "rust-analyzer.cargo.loadOutDirsFromCheck": true,
    "rust-analyzer.procMacro.enable": true,
}

[andrewwhitehead]

This just started showing up for me when importing types from the typenum crate. Strangely, if I change it to an unused import (use typenum::U16 when only U32 is referenced), that error seems to take priority over the unresolved type error.

[ecton]

I just started having this show up with use serde_derive::{Serialize, Deserialize}; -- given Serde's popularity, I suspect many others will run into this one, and the main reason for my comment is to try to help make it findable.

@bjorn3's suggestion of enabling procMacro support worked for me to alleviate the issue.

[jonas-schievink]

Is there any way to disable such errors, as it makes it vastly harder to see real errors from Rust Analyzer.

In the settings, add unresolved-import to the list of disabled diagnostics

[Veetaha]

I confirm that proc-macro-derives stopped working for me recently, not sure when exactly, but there should be some definite regression. All the necessary configurations are in place (loadOutDirsFromCheck and procMacro.enable):

[lnicola]

@Veetaha are you using nightly?

[Veetaha]

Yes, I always do

[lnicola]

#5651

Oh, it looks like I need to rebase it.