rust/tests/ui/copy-a-resource.rs

#[derive(Debug)]
struct Foo {
  i: isize,
}

impl Drop for Foo {
    fn drop(&mut self) {}
}

fn foo(i:isize) -> Foo {
    Foo {
        i: i
    }
}

fn main() {
    let x = foo(10);
    let _y = x.clone();
    //~^ ERROR no method named `clone` found
    println!("{:?}", x);
}
s/Show/Debug/g 2015-01-28 13:34:18 +00:00			`#[derive(Debug)]`
make non_camel_case_types an early lint 2018-12-17 03:21:47 +00:00			`struct Foo {`
Update compile fail tests to use isize. 2015-01-08 10:54:35 +00:00			`i: isize,`
Convert the test suite to use the Drop trait 2012-11-14 06:22:37 +00:00			`}`

make non_camel_case_types an early lint 2018-12-17 03:21:47 +00:00			`impl Drop for Foo {`
switch Drop to `&mut self` 2013-09-17 01:18:07 +00:00			`fn drop(&mut self) {}`
Enforce rule that classes with dtors aren't copyable The test for this is copy-a-resource. 2012-06-02 00:06:27 +00:00			`}`
Add test cases for resources 2011-06-28 15:47:56 +00:00
make non_camel_case_types an early lint 2018-12-17 03:21:47 +00:00			`fn foo(i:isize) -> Foo {`
			`Foo {`
Remove struct ctors 2012-09-05 22:58:43 +00:00			`i: i`
			`}`
			`}`

Fix subtle error in caching during kind computation that could cause linear values to be copied. Rewrite kind computation so that instead of directly computing the kind it computes what kinds of values are present in the type, and then derive kinds based on that. I find this easier to think about. Fixes #4821. 2013-02-08 03:33:12 +00:00			`fn main() {`
tests/tutorials: Get rid of `move`. 2013-02-15 10:44:18 +00:00			`let x = foo(10);`
librustc: Remove all uses of "copy". 2013-07-02 19:47:32 +00:00			`let _y = x.clone();`
Fix ICE that occurs when an associated const is ambiguous. Also change several error messages to refer to "items" rather than "methods", since associated items that require resolution during type checking are not always methods. 2015-05-03 05:30:59 +00:00			//~^ ERROR no method named `clone` found
core: split into fmt::Show and fmt::String fmt::Show is for debugging, and can and should be implemented for all public types. This trait is used with `{:?}` syntax. There still exists #[derive(Show)]. fmt::String is for types that faithfully be represented as a String. Because of this, there is no way to derive fmt::String, all implementations must be purposeful. It is used by the default format syntax, `{}`. This will break most instances of `{}`, since that now requires the type to impl fmt::String. In most cases, replacing `{}` with `{:?}` is the correct fix. Types that were being printed specifically for users should receive a fmt::String implementation to fix this. Part of #20013 [breaking-change] 2014-12-20 08:09:35 +00:00			`println!("{:?}", x);`
Fix subtle error in caching during kind computation that could cause linear values to be copied. Rewrite kind computation so that instead of directly computing the kind it computes what kinds of values are present in the type, and then derive kinds based on that. I find this easier to think about. Fixes #4821. 2013-02-08 03:33:12 +00:00			`}`