rust/tests/ui/unboxed-closures/unboxed-closures-generic.rs

// run-pass
use std::ops::FnMut;

fn call_it<F:FnMut(i32,i32)->i32>(y: i32, mut f: F) -> i32 {
    f(2, y)
}

pub fn main() {
    let f = |x: i32, y: i32| -> i32 { x + y };
    let z = call_it(3, f);
    println!("{}", z);
    assert_eq!(z, 5);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`// run-pass`
librustc: Implement unboxed closures with mutable receivers 2014-05-29 00:26:56 -05:00			`use std::ops::FnMut;`

Update test files; mostly the problem is that they were using the explicit form `Fn<A,B>` and now should use `Fn(A) -> B` or `Fn<A,Output=B>`, but in some cases we get duplicate error reports. This is mildly annoying and arises because of the main error and another error from the projection. Might be worth squashing those, but seems like a separate problem. 2015-01-12 09:27:25 -06:00			`fn call_it<F:FnMut(i32,i32)->i32>(y: i32, mut f: F) -> i32 {`
replace `f.call_mut(a, b, ..)` with `f(a, b, ..)` 2015-01-05 13:07:10 -06:00			`f(2, y)`
librustc: Implement unboxed closures with mutable receivers 2014-05-29 00:26:56 -05:00			`}`

			`pub fn main() {`
remove all kind annotations from closures 2015-02-01 11:44:15 -06:00			`let f = \|x: i32, y: i32\| -> i32 { x + y };`
librustc: Implement unboxed closures with mutable receivers 2014-05-29 00:26:56 -05:00			`let z = call_it(3, f);`
			`println!("{}", z);`
			`assert_eq!(z, 5);`
			`}`