Rustc reports errors for macro_rules that have attribute tags ([rustfmt::skip])

[Embers-of-the-Fire]

I tried this code:

#[macro_export]
#[rustfmt::skip]
macro_rules! test_macro {
    (()) => { Some(()) };
    (non) => { None };
}

fn main() {
    let t = crate::test_macro!(());
    println!("{:?}", t);
}

This does work if there's no [rustfmt::skip].
However, if this attribute is added, the following compilation error occurs:

error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
 --> src/main.rs:9:13
  |
9 |     let t = crate::test_macro!(());
  |             ^^^^^^^^^^^^^^^^^
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>
note: the macro is defined here
 --> src/main.rs:3:1
  |
3 | / macro_rules! test_macro {
4 | |     (()) => { Some(()) };
5 | |     (non) => { None };
6 | | }
  | |_^
  = note: `#[deny(macro_expanded_macro_exports_accessed_by_absolute_paths)]` on by default

And other commonly-used attributes do not fail, like feature or cfg.

Playground here: Rust Playground.

Note: the sequence of the two attributes does not make difference.

Meta

Stable(1.76.0), beta(1.77.0-beta.4 2/16) and nightly(1.78.0-nightly 2/15) all failed to compile this.

[fmease]

Related: #98291.

[Embers-of-the-Fire]

Related: #98291.

Looks like a duplicate, I'll close mine.