rust/tests/ui/should_assert_eq.stderr

error: use `assert_eq` for better reporting
  --> $DIR/should_assert_eq.rs:14:5
   |
14 |     assert!(1 == 2);
   |     ^^^^^^^^^^^^^^^^
   |
   = note: `-D should-assert-eq` implied by `-D warnings`
   = note: this error originates in a macro outside of the current crate

error: use `assert_eq` for better reporting
  --> $DIR/should_assert_eq.rs:15:5
   |
15 |     assert!(Debug(1) == Debug(2));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: use `assert_ne` for better reporting
  --> $DIR/should_assert_eq.rs:17:5
   |
17 |     assert!(Debug(1) != Debug(2));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: use `debug_assert_eq` for better reporting
  --> $DIR/should_assert_eq.rs:22:5
   |
22 |     debug_assert!(4 == 5);
   |     ^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: use `debug_assert_ne` for better reporting
  --> $DIR/should_assert_eq.rs:23:5
   |
23 |     debug_assert!(4 != 6);
   |     ^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: use `assert_eq` for better reporting
  --> $DIR/should_assert_eq.rs:27:5
   |
27 |     assert!(x == y);
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: use `assert_ne` for better reporting
  --> $DIR/should_assert_eq.rs:30:5
   |
30 |     assert!(x != y);
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate

error: aborting due to 7 previous errors