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

// error-pattern: copying a noncopyable value

struct r {
  b:bool,
  drop {}
}

fn main() {
    let i = move ~r { b: 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 05:39:20 -06:00			`// error-pattern: copying a noncopyable value`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 20:13:49 -05:00
Remove the class keyword 2012-08-15 20:46:55 -05:00			`struct r {`
Remove 'let' syntax for struct fields 2012-09-06 21:40:15 -05:00			`b:bool,`
Port more resource tests to classes 2012-06-01 22:21:59 -05:00			`drop {}`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 20:13:49 -05:00			`}`

			`fn main() {`
Remove uses of binary move - <- - from tests and libraries 2012-10-23 13:11:23 -05:00			`let i = move ~r { b: 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 05:39:20 -06:00			`let j = i;`
Register new snapshots, purge log_err and log_full in favour of log(...). 2011-12-22 19:53:53 -06:00			`log(debug, i);`
Unique pointers containing pinned kinds become pinned Issue #409 2011-09-23 20:13:49 -05:00			`}`