e734733a9e
This was missed in PR #75465. As a result, a few places have been using the full body span of functions, instead of just the header span.
39 lines
1.4 KiB
Text
39 lines
1.4 KiB
Text
error: `$x:expr` may be followed by `$y:tt`, which is not allowed for `expr` fragments
|
|
--> $DIR/same-sequence-span.rs:14:18
|
|
|
|
|
LL | (1 $x:expr $($y:tt,)*
|
|
| ^^^^^ not allowed after `expr` fragments
|
|
|
|
|
= note: allowed there are: `=>`, `,` or `;`
|
|
|
|
error: `$x:expr` may be followed by `=`, which is not allowed for `expr` fragments
|
|
--> $DIR/same-sequence-span.rs:15:18
|
|
|
|
|
LL | $(= $z:tt)*
|
|
| ^ not allowed after `expr` fragments
|
|
|
|
|
= note: allowed there are: `=>`, `,` or `;`
|
|
|
|
error: `$x:expr` may be followed by `$y:tt`, which is not allowed for `expr` fragments
|
|
--> $DIR/same-sequence-span.rs:19:1
|
|
|
|
|
LL | proc_macro_sequence::make_foo!();
|
|
| ---------------------------------^^^^^^^^^^^^^
|
|
| |
|
|
| not allowed after `expr` fragments
|
|
| in this macro invocation
|
|
|
|
|
= note: allowed there are: `=>`, `,` or `;`
|
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `$x:expr` may be followed by `=`, which is not allowed for `expr` fragments
|
|
--> $DIR/same-sequence-span.rs:19:1
|
|
|
|
|
LL | proc_macro_sequence::make_foo!();
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not allowed after `expr` fragments
|
|
|
|
|
= note: allowed there are: `=>`, `,` or `;`
|
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 4 previous errors
|
|
|