rust/tests/ui/generics/autobind.rs

// run-pass

fn f<T>(x: Vec<T>) -> T { return x.into_iter().next().unwrap(); }

fn g<F>(act: F) -> isize where F: FnOnce(Vec<isize>) -> isize { return act(vec![1, 2, 3]); }

pub fn main() {
    assert_eq!(g(f), 1);
    let f1 = f;
    assert_eq!(f1(vec!["x".to_string(), "y".to_string(), "z".to_string()]),
               "x".to_string());
}
tests: Add missing run-pass annotations 2019-07-27 00:54:25 +03:00			`// run-pass`

Fallout from renaming 2014-09-14 20:27:36 -07:00			`fn f<T>(x: Vec<T>) -> T { return x.into_iter().next().unwrap(); }`
Auto-bind generic functions when their value is taken in non-call context trans::trans_lval will now autobind if the given expression was the name of a generic functions. Those callees (trans_call and trans_bind) that are interested in the generics information call trans_lval_gen now. 2011-07-08 14:28:46 +02:00
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 22:54:04 +01:00			`fn g<F>(act: F) -> isize where F: FnOnce(Vec<isize>) -> isize { return act(vec![1, 2, 3]); }`
Auto-bind generic functions when their value is taken in non-call context trans::trans_lval will now autobind if the given expression was the name of a generic functions. Those callees (trans_call and trans_bind) that are interested in the generics information call trans_lval_gen now. 2011-07-08 14:28:46 +02:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
Use assert_eq! rather than assert! where possible 2013-05-18 22:02:45 -04:00			`assert_eq!(g(f), 1);`
fix rpass tests 2015-01-02 17:32:54 -05:00			`let f1 = f;`
std: Rename strbuf operations to string [breaking-change] 2014-05-25 03:17:19 -07:00			`assert_eq!(f1(vec!["x".to_string(), "y".to_string(), "z".to_string()]),`
			`"x".to_string());`
Change the ivec type syntax to [T]. This preserves the old syntax for now. 2011-07-18 08:41:35 -07:00			`}`