rust/tests/ui/macros/assert-eq-macro-success.rs

// run-pass
#[derive(PartialEq, Debug)]
struct Point { x : isize }

pub fn main() {
    assert_eq!(14,14);
    assert_eq!("abc".to_string(),"abc".to_string());
    assert_eq!(Box::new(Point{x:34}),Box::new(Point{x:34}));
    assert_eq!(&Point{x:34},&Point{x:34});
    assert_eq!(42, 42, "foo bar");
    assert_eq!(42, 42, "a {} c", "b");
    assert_eq!(42, 42, "{x}, {y}, {z}", x = 1, y = 2, z = 3);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`// run-pass`
s/Show/Debug/g 2015-01-28 08:34:18 -05:00			`#[derive(PartialEq, Debug)]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`struct Point { x : isize }`
add assert_eq! macro the assert_eq! macro compares its arguments and fails if they're not equal. It's more informative than fail_unless!, because it explicitly writes the given and expected arguments on failure. 2013-03-13 12:10:32 -07:00
testsuite: more `pub fn main` 2013-03-27 09:58:28 -07:00			`pub fn main() {`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`assert_eq!(14,14);`
std: Remove String's to_owned 2014-05-25 03:10:11 -07:00			`assert_eq!("abc".to_string(),"abc".to_string());`
Switched to Box::new in many places. Many of the modifications putting in `Box::new` calls also include a pointer to Issue 22405, which tracks going back to `box <expr>` if possible in the future. (Still tried to use `Box<_>` where it sufficed; thus some tests still have `box_syntax` enabled, as they use a mix of `box` and `Box::new`.) Precursor for overloaded-`box` and placement-`in`; see Issue 22181. 2015-02-15 09:52:21 +01:00			`assert_eq!(Box::new(Point{x:34}),Box::new(Point{x:34}));`
add assert_eq! macro the assert_eq! macro compares its arguments and fails if they're not equal. It's more informative than fail_unless!, because it explicitly writes the given and expected arguments on failure. 2013-03-13 12:10:32 -07:00			`assert_eq!(&Point{x:34},&Point{x:34});`
Add message argument to `assert_eq` macro 2016-05-31 01:53:14 +09:00			`assert_eq!(42, 42, "foo bar");`
			`assert_eq!(42, 42, "a {} c", "b");`
			`assert_eq!(42, 42, "{x}, {y}, {z}", x = 1, y = 2, z = 3);`
add assert_eq! macro the assert_eq! macro compares its arguments and fails if they're not equal. It's more informative than fail_unless!, because it explicitly writes the given and expected arguments on failure. 2013-03-13 12:10:32 -07:00			`}`