cfg resolve diagnostic doesn't show up for axum macro

[joshka]

Code

Without the macro feature enabled.

use axum::extract::FromRef;

#[derive(Clone, FromRef)]
struct AppState {
    db: SqlitePool,
}

Current output

error: cannot find derive macro `FromRef` in this scope
  --> src/main.rs:33:17
   |
33 | #[derive(Clone, FromRef)]
   |                 ^^^^^^^
   |
note: `FromRef` is imported here, but it is only a trait, without a derive macro
  --> src/main.rs:1:12
   |
1  | use axum::{extract::FromRef, Router};
   |            ^^^^^^^^^^^^^^^^

Desired output

error[E0432]: unresolved import `axum::extract::FromRef`
  --> src/main.rs:2:5
   |
2  | use axum::extract::FromRef;
   |     ^^^^^^^^^^^^^^^^^ no `FromRef` in `extract`
   |
note: found an item that was configured out
  --> /Users/joshka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-0.7.9/src/extract/mod.rs:xx:yy
   |
xx | macro_rules! FromRef;
   |         ^^
note: the item is gated behind the `macros` feature
  --> /Users/joshka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-0.7.9/src/extract/mod.rs:xx:yy

Rationale and extra context

The detection of cfg'd out items should treat items that match the expected type (e.g. a macro) as higher priority than items which match the name (e.g. FromRef)

Other cases

Rust Version

rustc --version --verbose
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1

Anything else?

Similar to but not the same as #132166
Possibly relevant to #129183

[Noratrieb]

I think this is caused by an entirely different root cause and the duplicate name is a red herring, it shouldn't matter to resolve whether there's an item of the same name already in a different namespace.
I remember this working correctly for serde, which uses the same pattern.