rust/tests/ui/unboxed-closures/unboxed-closures-static-call-wrong-trait.rs

#![feature(unboxed_closures, tuple_trait)]

fn to_fn_mut<A:std::marker::Tuple,F:FnMut<A>>(f: F) -> F { f }

fn main() {
    let mut_ = to_fn_mut(|x| x);
    mut_.call((0, )); //~ ERROR no method named `call` found
}
Adjust diagnostics, bless tests 2022-07-30 05:37:48 +00:00			`#![feature(unboxed_closures, tuple_trait)]`
librustc: When checking static method calls to unboxed closures, look at the right trait and take the method name into account. Closes #16599. 2014-08-20 16:12:16 +00:00
Adjust diagnostics, bless tests 2022-07-30 05:37:48 +00:00			`fn to_fn_mut<A:std::marker::Tuple,F:FnMut<A>>(f: F) -> F { f }`
Update compile-fail tests to use the expected type to force the closure kind, thereby detecting what happens if there are mismatches. Simply removing the `:` annotations caused most of these tests to pass or produce other errors, because the inference would convert the closure into a more appropriate kind. (The ability to override the inference by using the expected type is an important backdoor partly for this reason.) 2015-02-03 16:32:26 +00:00
librustc: When checking static method calls to unboxed closures, look at the right trait and take the method name into account. Closes #16599. 2014-08-20 16:12:16 +00:00			`fn main() {`
Update compile-fail tests to use the expected type to force the closure kind, thereby detecting what happens if there are mismatches. Simply removing the `:` annotations caused most of these tests to pass or produce other errors, because the inference would convert the closure into a more appropriate kind. (The ability to override the inference by using the expected type is an important backdoor partly for this reason.) 2015-02-03 16:32:26 +00:00			`let mut_ = to_fn_mut(\|x\| x);`
Fix ICE that occurs when an associated const is ambiguous. Also change several error messages to refer to "items" rather than "methods", since associated items that require resolution during type checking are not always methods. 2015-05-03 05:30:59 +00:00			mut_.call((0, )); //~ ERROR no method named `call` found
librustc: When checking static method calls to unboxed closures, look at the right trait and take the method name into account. Closes #16599. 2014-08-20 16:12:16 +00:00			`}`