2020-04-16 06:50:32 +00:00
|
|
|
// run-fail
|
Cleaner assert_eq! & assert_ne! panic messages
Modify panic message for `assert_eq!`, `assert_ne!`, the currently unstable `assert_matches!`, as well as the corresponding `debug_assert_*` macros.
```rust
assert_eq!(1 + 1, 3);
assert_eq!(1 + 1, 3, "my custom message value={}!", 42);
```
```plain
thread 'main' panicked at $DIR/main.rs:6:5:
assertion failed: `(left == right)`
left: `2`,
right: `3`
```
```plain
thread 'main' panicked at $DIR/main.rs:6:5:
assertion failed: `(left == right)`
left: `2`,
right: `3`: my custom message value=42!
```
```plain
thread 'main' panicked at $DIR/main.rs:6:5:
assertion `left == right` failed
left: 2
right: 3
```
```plain
thread 'main' panicked at $DIR/main.rs:6:5:
assertion `left == right` failed: my custom message value=42!
left: 2
right: 3
```
This PR is a simpler subset of the #111030, but it does NOT stringify the original left and right source code assert expressions, thus should be faster to compile.
2023-05-01 16:34:42 +00:00
|
|
|
// error-pattern:assertion `left == right` failed
|
|
|
|
|
// error-pattern: left: 14
|
|
|
|
|
// error-pattern: right: 15
|
2020-05-07 15:39:02 +00:00
|
|
|
// ignore-emscripten no processes
|
2013-03-13 19:10:32 +00:00
|
|
|
|
|
|
|
|
fn main() {
|
2016-05-27 02:39:36 +00:00
|
|
|
assert_eq!(14, 15);
|
2013-03-13 19:10:32 +00:00
|
|
|
}
|
