rust/tests/ui/functions-closures/closure-inference.rs

//@ run-pass
#![allow(unused_braces)]

fn foo(i: isize) -> isize { i + 1 }

fn apply<A, F>(f: F, v: A) -> A where F: FnOnce(A) -> A { f(v) }

pub fn main() {
    let f = {|i| foo(i)};
    assert_eq!(apply(f, 2), 3);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
update tests 2020-03-27 21:56:19 +01:00			`#![allow(unused_braces)]`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
Teach project to unify the return type even if a precise match is not possible. There is some amount of duplication as a result (similar to select) -- I am not happy about this but not sure how to fix it without deeper rewrites. 2015-02-03 06:12:43 -05:00			`fn foo(i: isize) -> isize { i + 1 }`
new test showing off the improved inference 2012-02-05 09:56:18 -08:00
fix rpass tests 2015-01-02 17:32:54 -05:00			`fn apply<A, F>(f: F, v: A) -> A where F: FnOnce(A) -> A { f(v) }`
new test showing off the improved inference 2012-02-05 09:56:18 -08:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
Allow closure arguments types to unify even if we can't fully resolve a trait obligation. Partial fix for #16440 -- closure return types are not handled yet. 2015-02-02 11:52:08 -05:00			`let f = {\|i\| foo(i)};`
Use assert_eq! rather than assert! where possible 2013-05-18 22:02:45 -04:00			`assert_eq!(apply(f, 2), 3);`
new test showing off the improved inference 2012-02-05 09:56:18 -08:00			`}`