rust/tests/ui/fn/issue-3044.rs

fn main() {
    let needlesArr: Vec<char> = vec!['a', 'f'];
    needlesArr.iter().fold(|x, y| {
        //~^ ERROR this method takes 2 arguments but 1 argument was supplied
    });
}
When checking loop bodies and do-expr bodies, don't require the expected type to exist If the expected type is none (due to a type error), we shouldn't fail with an ICE, but rather, just print out another type error. Changed the do-expr type error message to make sense in this context (see the test case for how it works). Closes #3044. 2012-08-02 18:11:29 -07:00			`fn main() {`
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			`let needlesArr: Vec<char> = vec!['a', 'f'];`
remove all kind annotations from closures 2015-02-01 12:44:15 -05:00			`needlesArr.iter().fold(\|x, y\| {`
Tweak wording of fn call with wrong number of args 2023-01-05 03:02:10 +00:00			`//~^ ERROR this method takes 2 arguments but 1 argument was supplied`
Remove do keyword from test/ 2014-01-27 18:29:50 -05:00			`});`
When checking loop bodies and do-expr bodies, don't require the expected type to exist If the expected type is none (due to a type error), we shouldn't fail with an ICE, but rather, just print out another type error. Changed the do-expr type error message to make sense in this context (see the test case for how it works). Closes #3044. 2012-08-02 18:11:29 -07:00			`}`