Macros not resolving

[MaxBeaud]

At the beginning of my program: use statement and start of the main function, rust-analyzer tells me it has failed to import certain macros. However this is purely rust-analyzer as the program can compile with no problem and the compiler throws no error.

[bjorn3]

You can enable proc-macro support using

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

[erichgess]

I'm having the same issue, but enabling those two features did not resolve the errors.

[flodiebold]

This is probably a duplicate of #6716. It should be fixed on nightly, or with the release tomorrow.

[erichgess]

I updated my VSCode settings to use nightly (VSCode now shows the version as rust-analyzer version: nightly (4998807)), but I still get the error.

[AngelOfSol]

I tried updating to nightly, because I have a similar issue, but some macro imports are still broken for me:

RA tends to highlight them only when a file that has the errors in question gets opened, and it only seems to be broken for one package (in my case).

[flodiebold]

@AngelOfSol do you have the settings mentioned above turned on?

@erichgess Can you provide more information about which errors you're still seeing? These errors aren't all the same bug.

[AngelOfSol]

@fannheyward Yes I do, this is my settings list:

{
    "editor.formatOnSave": true,
    "workbench.colorTheme": "Monokai Pro (Filter Spectrum)",
    "vim.useCtrlKeys": false,
    "window.zoomLevel": 0,
    "rust-analyzer.excludeGlobs": [
        "resources/*",
    ],
    "rust-analyzer.checkOnSave.overrideCommand": null,
    "rust-analyzer.files.watcher": "notify",
    "rust-analyzer.cargo.loadOutDirsFromCheck": true,
    "rust-analyzer.procMacro.enable": true,
    "rust-analyzer.files.exclude": [
        "resources/*"
    ],
    "editor.fontSize": 18,
    "rust-analyzer.checkOnSave.command": "clippy",
    "rust-analyzer.cargo.allFeatures": true,
    "rust-analyzer.updates.channel": "nightly"
}

[rimutaka]

Version: v0.3.415-nightly

Doesn't seem to resolve any macro's for me at all.

use tracing::{info, trace};
info!(
            "Loading config file for file_types from {} and munchers from {}",
            file_type_dir, muncher_dir
        );

error: could not resolve macro 'callsite'

[flodiebold]

@rimutaka I can't reproduce this. Note that function-local imports don't work, but if the use is outside the function, the tracing::info macro works for me. Please open a separate issue with a minimal reproduction if you're still experiencing this on current nightly.

@MaxBeaud Is this still happening for you on the current version?

[AngelOfSol]

Here's a git repo that is a minimal repro of my issue: https://github.com/AngelOfSol/strum-macro-not-resolve, it has a capture of what my VS-Code looks like at when looking at the src file.

[yaymukund]

I experience the same behavior when using crossterm's queue!() macro. Rust analyzer (nightly at eb9ba45) complains that write_ansi_code isn't found. Here's a minimal repro which also includes a png of my error in vim:

https://git.sr.ht/~yaymukund/crossterm-macro-not-resolve
https://github.com/crossterm-rs/crossterm/blob/0.18/src/macros.rs#L131

[flodiebold]

@AngelOfSol This might be caused by the way the strum proc macro is defined, since we don't support cfg_attr yet. Could you open a separate issue for your problem?

@yaymukund The queue! macro expands to a local use $crate::{write_ansi_code, Command} internally, and we don't support local imports yet (#1165).

[wpbrown]

I've been using nightly for months and seeing the issues from cfg_attr on strum, but as of latest nightly (nightly (554dd21)) now also seeing no macros working even slog::info, similiar to @rimutaka above. Stable is okay.

[flodiebold]

@wpbrown can you please provide a minimal reproduction, in a separate issue?

[flodiebold]

I'm going to close this issue because I believe the original problem was fixed, and this is becoming a general dumping ground for macro error false positives.

[MaxBeaud]

@flodiebold In my case, I just downloaded the rust-analyzer update on vsCode and my using statement errors are gone. Furthermore the update for some reason caught some oddities it didn't before and has fixed some UB I could not for the life of me find out what it's cause was. I realize this issue is closed however, thank you.