`missing_fragment_specifier` points at the wrong span if followed by another metavariable

[tgross35]

This:

macro_rules! foo {
    ($bar) => {};
    ($baz $qux:ident) => {};
}

Produces:

error: missing fragment specifier
 --> src/lib.rs:2:6
  |
2 |     ($bar) => {};
  |      ^^^^

...

error: missing fragment specifier
 --> src/lib.rs:3:11
  |
3 |     ($baz $qux:ident) => {};
  |           ^

Notice for the second pattern, the diagnostic points at $qux rather than $baz. $qux is not a problem here, the span should look similar to $bar.

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=11ae576f5ce6e77fbad782f6c013ba76

Tested on both 1.80 and the 2024-08-13 nightly. This affects the new diagnostic that applies to e2024 added in #128006, as well as the existing lint (I noticed it looking at the reports in #128425).

[tgross35]

It seems like the span at https://github.com/tgross35/rust/blob/2b78d920964e1d70927bcd208529bda0e11120d0/compiler/rustc_expand/src/mbe/macro_check.rs#L268 must be wrong, which means this might show up in other diagnostics too.

[fmease]

Duplicate of #95463.

[tgross35]

Ah yup, thanks.