rust/src/test/compile-fail/unique-pinned-nocopy.rs

// error-pattern: copying a noncopyable value

struct r {
  let b:bool;
  new(b: bool) { self.b = b; }
  drop {}
}

fn main() {
    let i <- ~r(true);
    let j = i;
    log(debug, i);
}
Update stdlib, compiler, and tests to new kind system This involved adding 'copy' to more generics than I hoped, but an experiment with making it implicit showed that that way lies madness -- unless enforced, you will not remember to mark functions that don't copy as not requiring copyable kind. Issue #1177 2011-11-18 12:39:20 +01:00			`// error-pattern: copying a noncopyable value`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 18:13:49 -07:00
Remove the class keyword 2012-08-15 18:46:55 -07:00			`struct r {`
Port more resource tests to classes 2012-06-01 20:21:59 -07:00			`let b:bool;`
			`new(b: bool) { self.b = b; }`
			`drop {}`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 18:13:49 -07:00			`}`

			`fn main() {`
Make some nocopy tests a bit more futureproof Turn the let assignment initializers into move initializers since that assignment is going to become illegal 2011-09-26 21:17:11 -07:00			`let i <- ~r(true);`
Update stdlib, compiler, and tests to new kind system This involved adding 'copy' to more generics than I hoped, but an experiment with making it implicit showed that that way lies madness -- unless enforced, you will not remember to mark functions that don't copy as not requiring copyable kind. Issue #1177 2011-11-18 12:39:20 +01:00			`let j = i;`
Register new snapshots, purge log_err and log_full in favour of log(...). 2011-12-22 17:53:53 -08:00			`log(debug, i);`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 18:13:49 -07:00			`}`