mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-22 23:04:33 +00:00
c9886a1ddf
We are moving toward forbidding `missing_fragment_specifier` either in edition 2024 or unconditionally. Make a first step toward this by ensuring crates that rely on the old behavior are reported when used as dependencies. Tracking issue: <https://github.com/rust-lang/rust/issues/128143>
24 lines
964 B
Plaintext
24 lines
964 B
Plaintext
error: missing fragment specifier
|
|
--> $DIR/issue-39404.rs:3:19
|
|
|
|
|
LL | macro_rules! m { ($i) => {} }
|
|
| ^^
|
|
|
|
|
= 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 #40107 <https://github.com/rust-lang/rust/issues/40107>
|
|
= note: `#[deny(missing_fragment_specifier)]` on by default
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
Future incompatibility report: Future breakage diagnostic:
|
|
error: missing fragment specifier
|
|
--> $DIR/issue-39404.rs:3:19
|
|
|
|
|
LL | macro_rules! m { ($i) => {} }
|
|
| ^^
|
|
|
|
|
= 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 #40107 <https://github.com/rust-lang/rust/issues/40107>
|
|
= note: `#[deny(missing_fragment_specifier)]` on by default
|
|
|