rust/tests/ui/macros/assert-ne-macro-panic.rs

// run-fail
// error-pattern:assertion `left != right` failed
// error-pattern:  left: 14
// error-pattern: right: 14
// ignore-emscripten no processes

fn main() {
    assert_ne!(14, 14);
}
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09: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 12:34:42 -04:00			// error-pattern:assertion `left != right` failed
			`// error-pattern: left: 14`
			`// error-pattern: right: 14`
Skip tests on emscripten 2020-05-08 00:39:02 +09:00			`// ignore-emscripten no processes`
updated assert_eq test, fixed incorrect assert_ne message and added test. 2017-06-13 14:17:59 +01:00
			`fn main() {`
			`assert_ne!(14, 14);`
			`}`