mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-26 16:54:01 +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>
30 lines
1.1 KiB
Plaintext
30 lines
1.1 KiB
Plaintext
error: missing fragment specifier
|
|
--> $DIR/macro-missing-fragment-deduplication.rs:4:6
|
|
|
|
|
LL | ($name) => {}
|
|
| ^^^^^
|
|
|
|
error: missing fragment specifier
|
|
--> $DIR/macro-missing-fragment-deduplication.rs:4:6
|
|
|
|
|
LL | ($name) => {}
|
|
| ^^^^^
|
|
|
|
|
= 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 2 previous errors
|
|
|
|
Future incompatibility report: Future breakage diagnostic:
|
|
error: missing fragment specifier
|
|
--> $DIR/macro-missing-fragment-deduplication.rs:4:6
|
|
|
|
|
LL | ($name) => {}
|
|
| ^^^^^
|
|
|
|
|
= 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
|
|
|