rust/src/test/ui/borrowck/borrowck-move-moved-value-into-closure.rs

// revisions: ast mir
//[mir]compile-flags: -Z borrowck=mir

#![feature(box_syntax)]

fn call_f<F:FnOnce() -> isize>(f: F) -> isize {
    f()
}

fn main() {
    let t: Box<_> = box 3;

    call_f(move|| { *t + 1 });
    call_f(move|| { *t + 1 }); //[ast]~ ERROR capture of moved value
    //[mir]~^ ERROR use of moved value
}
handle gen/kill sets together 2017-12-03 17:00:46 -06:00			`// revisions: ast mir`
			`//[mir]compile-flags: -Z borrowck=mir`

Test fixes and rebase conflicts 2015-01-07 20:53:58 -06:00			`#![feature(box_syntax)]`

Update compile fail tests to use isize. 2015-01-08 04:54:35 -06:00			`fn call_f<F:FnOnce() -> isize>(f: F) -> isize {`
Issue #7444 - Borrowck permits moved values to be captured 2013-07-17 06:19:43 -05:00			`f()`
			`}`

			`fn main() {`
Add `: Box<_>` or `::Box<_>` type annotations to various places. This is the kind of change that one is expected to need to make to accommodate overloaded-`box`. ---- Note that this is not all of the changes necessary to accommodate Issue 22181. It is merely the subset of those cases where there was already a let-binding in place that made it easy to add the necesasry type ascription. (For unnamed intermediate `Box` values, one must go down a different route; `Box::new` is the option that maximizes portability, but has potential inefficiency depending on whether the call is inlined.) ---- There is one place worth note, `run-pass/coerce-match.rs`, where I used an ugly form of `Box<_>` type ascription where I would have preferred to use `Box::new` to accommodate overloaded-`box`. I deliberately did not use `Box::new` here, because that is already done in coerce-match-calls.rs. ---- Precursor for overloaded-`box` and placement-`in`; see Issue 22181. 2015-02-17 14:41:32 -06:00			`let t: Box<_> = box 3;`
Issue #7444 - Borrowck permits moved values to be captured 2013-07-17 06:19:43 -05:00
Mostly rote conversion of `proc()` to `move\|\|` (and occasionally `Thunk::new`) 2014-11-26 07:12:18 -06:00			`call_f(move\|\| { *t + 1 });`
handle gen/kill sets together 2017-12-03 17:00:46 -06:00			`call_f(move\|\| { *t + 1 }); //[ast]~ ERROR capture of moved value`
			`//[mir]~^ ERROR use of moved value`
Issue #7444 - Borrowck permits moved values to be captured 2013-07-17 06:19:43 -05:00			`}`