mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-16 10:35:22 +00:00
4698b366c4
When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
85 lines
3.1 KiB
Plaintext
85 lines
3.1 KiB
Plaintext
error: `assert!(true)` will be optimized out by the compiler
|
|
--> $DIR/assertions_on_constants.rs:11:5
|
|
|
|
|
LL | assert!(true);
|
|
| ^^^^^^^^^^^^^^
|
|
|
|
|
= note: `-D clippy::assertions-on-constants` implied by `-D warnings`
|
|
= help: remove it
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(false)` should probably be replaced
|
|
--> $DIR/assertions_on_constants.rs:12:5
|
|
|
|
|
LL | assert!(false);
|
|
| ^^^^^^^^^^^^^^^
|
|
|
|
|
= help: use `panic!()` or `unreachable!()`
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(true)` will be optimized out by the compiler
|
|
--> $DIR/assertions_on_constants.rs:13:5
|
|
|
|
|
LL | assert!(true, "true message");
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
= help: remove it
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(false, "false message")` should probably be replaced
|
|
--> $DIR/assertions_on_constants.rs:14:5
|
|
|
|
|
LL | assert!(false, "false message");
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
= help: use `panic!("false message")` or `unreachable!("false message")`
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(false, msg.to_uppercase())` should probably be replaced
|
|
--> $DIR/assertions_on_constants.rs:17:5
|
|
|
|
|
LL | assert!(false, msg.to_uppercase());
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
= help: use `panic!(msg.to_uppercase())` or `unreachable!(msg.to_uppercase())`
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(true)` will be optimized out by the compiler
|
|
--> $DIR/assertions_on_constants.rs:20:5
|
|
|
|
|
LL | assert!(B);
|
|
| ^^^^^^^^^^^
|
|
|
|
|
= help: remove it
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(false)` should probably be replaced
|
|
--> $DIR/assertions_on_constants.rs:23:5
|
|
|
|
|
LL | assert!(C);
|
|
| ^^^^^^^^^^^
|
|
|
|
|
= help: use `panic!()` or `unreachable!()`
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `assert!(false, "C message")` should probably be replaced
|
|
--> $DIR/assertions_on_constants.rs:24:5
|
|
|
|
|
LL | assert!(C, "C message");
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
= help: use `panic!("C message")` or `unreachable!("C message")`
|
|
= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: `debug_assert!(true)` will be optimized out by the compiler
|
|
--> $DIR/assertions_on_constants.rs:26:5
|
|
|
|
|
LL | debug_assert!(true);
|
|
| ^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
= help: remove it
|
|
= note: this error originates in the macro `$crate::assert` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 9 previous errors
|
|
|