`.await` completion shown in a non-async function when the receiver is of unknown type

[ada4a]

code snippet to reproduce:

//- minicore: future
fn foo(t: T) {
    let _ = t.$0;
}

t is of type T which isn't defined anywhere, which in turn causes a completion t.await to appear. If we define T, e.g. by adding it as a generic to foo, then the completion is (correctly) no longer shown.

rust-analyzer version: rust-analyzer 1.95.0 (5980761 2026-04-14)

rustc version: rustc 1.95.0 (59807616e 2026-04-14)

editor or extension: VSCode, extension version 0.3.2913

relevant settings: none

@rustbot claim

[ChayimFriedman2]

The general case is due to a trait solver bug (see rust-lang/rust#150453, we have many more issues about this). This specific case though (a direct error type) won't be fixed by that PR, so we need to guard against it in r-a (not suggest methods in hir/src/lib.rs if the type is an error type).

[ada4a]

Thank you for the context!

not suggest methods in hir/src/lib.rs if the type is an error type

Great, that was my idea as well:)