mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-02 03:33:59 +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>
42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
error: expected identifier, found `+`
|
|
--> $DIR/issue-33569.rs:2:8
|
|
|
|
|
LL | { $+ } => {
|
|
| ^
|
|
|
|
error: expected one of: `*`, `+`, or `?`
|
|
--> $DIR/issue-33569.rs:6:13
|
|
|
|
|
LL | $(x)(y)
|
|
| ^^^
|
|
|
|
error: missing fragment specifier
|
|
--> $DIR/issue-33569.rs:2:8
|
|
|
|
|
LL | { $+ } => {
|
|
| ^
|
|
|
|
error: missing fragment specifier
|
|
--> $DIR/issue-33569.rs:2:8
|
|
|
|
|
LL | { $+ } => {
|
|
| ^
|
|
|
|
|
= 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 4 previous errors
|
|
|
|
Future incompatibility report: Future breakage diagnostic:
|
|
error: missing fragment specifier
|
|
--> $DIR/issue-33569.rs:2:8
|
|
|
|
|
LL | { $+ } => {
|
|
| ^
|
|
|
|
|
= 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
|
|
|