rust/library/core/tests/clone.rs

#[test]
fn test_borrowed_clone() {
    let x = 5;
    let y: &i32 = &x;
    let z: &i32 = (&y).clone();
    assert_eq!(*z, 5);
}

#[test]
fn test_clone_from() {
    let a = Box::new(5);
    let mut b = Box::new(10);
    b.clone_from(&a);
    assert_eq!(*b, 5);
}
Extract tests from libcore to a separate crate Libcore's test infrastructure is complicated by the fact that many lang items are defined in the crate. The current approach (realcore/realstd imports) is hacky and hard to work with (tests inside of core::cmp haven't been run for months!). Moving tests to a separate crate does mean that they can only test the public API of libcore, but I don't feel that that is too much of an issue. The only tests that I had to get rid of were some checking the various numeric formatters, but those are also exercised through normal format! calls in other tests. 2014-06-28 13:57:36 -07:00			`#[test]`
			`fn test_borrowed_clone() {`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`let x = 5;`
Add unused modules to libcoretest 2015-10-15 21:07:20 +02:00			`let y: &i32 = &x;`
			`let z: &i32 = (&y).clone();`
Extract tests from libcore to a separate crate Libcore's test infrastructure is complicated by the fact that many lang items are defined in the crate. The current approach (realcore/realstd imports) is hacky and hard to work with (tests inside of core::cmp haven't been run for months!). Moving tests to a separate crate does mean that they can only test the public API of libcore, but I don't feel that that is too much of an issue. The only tests that I had to get rid of were some checking the various numeric formatters, but those are also exercised through normal format! calls in other tests. 2014-06-28 13:57:36 -07:00			`assert_eq!(*z, 5);`
			`}`

			`#[test]`
			`fn test_clone_from() {`
Use Box::new() instead of box syntax in core tests 2022-05-29 00:40:47 +02:00			`let a = Box::new(5);`
			`let mut b = Box::new(10);`
Extract tests from libcore to a separate crate Libcore's test infrastructure is complicated by the fact that many lang items are defined in the crate. The current approach (realcore/realstd imports) is hacky and hard to work with (tests inside of core::cmp haven't been run for months!). Moving tests to a separate crate does mean that they can only test the public API of libcore, but I don't feel that that is too much of an issue. The only tests that I had to get rid of were some checking the various numeric formatters, but those are also exercised through normal format! calls in other tests. 2014-06-28 13:57:36 -07:00			`b.clone_from(&a);`
			`assert_eq!(*b, 5);`
			`}`