Macro error with futures::try_join!

[lnicola]

Same as @jeromegn , I am still getting the error on the nightly version of rust-analyzer, in my case in a call to futures::try_join!.

Originally posted by @Victor-Savu in #6716 (comment)

[peku33]

Same here.
This affect all futures macros, like select, join etc.

[edwin0cheng]

Maybe related to #6811

[flodiebold]

@Victor-Savu @peku33 Please check this again with the next nightly or current master.

[Victor-Savu]

Unfortunately I can still reproduce the problem. Here is a minimal reproduction:

Extension version: 0.3.418-nightly

cargo.toml:

[package]
name = "rust-analyzer-error"
version = "0.1.0"
edition = "2018"

[dependencies]
tokio = { version = "0.2", features = ["macros"] }
futures = "0.3"

main.rs:

#[tokio::main]
async fn main() {
    futures::join!(
        async {
            println!("Hello, world!");
        },
        async {
            println!("Hello, world!");
        }
    );
}

I used join! instead of try_join! to keep the example as short as possible but the error is the similar:

could not resolve macro $crate::join_internal

[flodiebold]

join_internal seems to be a proc_macro_hack macro; that's probably the problem.

[peku33]

So this is a problem with rust-analyzer or futures?
At the moment one of the most popular crates with 3M recent downloads (futures) triggers this error for basic usage.

[flodiebold]

Any error that rust-analyzer produces in code that compiles is a problem in rust-analyzer.

You can disable the diagnostic by adding macro-error to the rust-analyzer.diagnostics.disabled setting.

[lnicola]

Triage: this still happens even after #7145.

[lnicola]

Ah, it's a proc_macro_hack thing.