Rust-analyzer throws "unresolved-macro" despite disabling "macro-error" and "unresolved-macro-call"

Question

I'm writing some backend code in rust using VSCode and of course the rust-analyzer. As many others, I have gotten issues with linting of macros by rust-anylyzer. I tried suppressing the linting/errors in settings.json, but with very little success.

    "editor.defaultFormatter": "matklad.rust-analyzer",
    "rust-analyzer.diagnostics.disabled": [
        "macro-error",
        "unresolved-macro-call",
        "unresolved-import"
    ],
    "rust-analyzer.experimental.procAttrMacros": false,
    "rust-analyzer.procMacro.enable": false

Yet somehow I still receive linting and error displays of unresolved-macro-errors.

I have also tried setting procAttrMacros and procMacro.enable to true, error still occurs. All github/so-questions related to the matter just suggest fiddling with rust-analyzer.diagnostics.disabled property, which I have, but that has not fixed the issue.

What am I doing wrong?

Just double checking, does `cargo check` return these errors? or is it just rust-analyzer? — kmdreko, Dec 16 '21 at 22:20
Just ran it, it is *only* rust-analyzer that returns these errors. Cargo check returns no issues. The project also compiles without issue with cargo run — Philipp Doerner, Dec 17 '21 at 17:16
Ur settings are working for me. After restart of VSCode my warnings vanished — Boris Ivanov, Mar 04 '22 at 11:20

Rust-analyzer throws "unresolved-macro" despite disabling "macro-error" and "unresolved-macro-call"

0 Answers0