rust/tests/ui/span/issue-34264.rs

fn foo(Option<i32>, String) {} //~ ERROR expected one of
//~^ ERROR expected one of
fn bar(x, y: usize) {} //~ ERROR expected one of

fn main() {
    foo(Some(42), 2);
    foo(Some(42), 2, ""); //~ ERROR function takes
    bar("", ""); //~ ERROR mismatched types
    bar(1, 2);
    bar(1, 2, 3); //~ ERROR function takes
}
Merge cfail and ui tests into ui tests 2017-11-20 12:13:27 +00:00			`fn foo(Option<i32>, String) {} //~ ERROR expected one of`
			`//~^ ERROR expected one of`
			`fn bar(x, y: usize) {} //~ ERROR expected one of`
Introduce `TyErr` independent from `TyInfer` Add a `TyErr` type to represent unknown types in places where parse errors have happened, while still able to build the AST. Initially only used to represent incorrectly written fn arguments and avoid "expected X parameters, found Y" errors when called with the appropriate amount of parameters. We cannot use `TyInfer` for this as `_` is not allowed as a valid argument type. Example output: ```rust error: expected one of `:` or `@`, found `,` --> file.rs:12:9 \| 12 \| fn bar(x, y: usize) {} \| ^ error[E0061]: this function takes 2 parameters but 3 parameters were supplied --> file.rs:19:9 \| 12 \| fn bar(x, y) {} \| --------------- defined here ... 19 \| bar(1, 2, 3); \| ^^^^^^^ expected 2 parameters ``` 2017-03-29 01:56:29 +00:00
			`fn main() {`
			`foo(Some(42), 2);`
Tweak wording of fn call with wrong number of args 2023-01-05 03:02:10 +00:00			`foo(Some(42), 2, ""); //~ ERROR function takes`
Merge cfail and ui tests into ui tests 2017-11-20 12:13:27 +00:00			`bar("", ""); //~ ERROR mismatched types`
Introduce `TyErr` independent from `TyInfer` Add a `TyErr` type to represent unknown types in places where parse errors have happened, while still able to build the AST. Initially only used to represent incorrectly written fn arguments and avoid "expected X parameters, found Y" errors when called with the appropriate amount of parameters. We cannot use `TyInfer` for this as `_` is not allowed as a valid argument type. Example output: ```rust error: expected one of `:` or `@`, found `,` --> file.rs:12:9 \| 12 \| fn bar(x, y: usize) {} \| ^ error[E0061]: this function takes 2 parameters but 3 parameters were supplied --> file.rs:19:9 \| 12 \| fn bar(x, y) {} \| --------------- defined here ... 19 \| bar(1, 2, 3); \| ^^^^^^^ expected 2 parameters ``` 2017-03-29 01:56:29 +00:00			`bar(1, 2);`
Tweak wording of fn call with wrong number of args 2023-01-05 03:02:10 +00:00			`bar(1, 2, 3); //~ ERROR function takes`
Introduce `TyErr` independent from `TyInfer` Add a `TyErr` type to represent unknown types in places where parse errors have happened, while still able to build the AST. Initially only used to represent incorrectly written fn arguments and avoid "expected X parameters, found Y" errors when called with the appropriate amount of parameters. We cannot use `TyInfer` for this as `_` is not allowed as a valid argument type. Example output: ```rust error: expected one of `:` or `@`, found `,` --> file.rs:12:9 \| 12 \| fn bar(x, y: usize) {} \| ^ error[E0061]: this function takes 2 parameters but 3 parameters were supplied --> file.rs:19:9 \| 12 \| fn bar(x, y) {} \| --------------- defined here ... 19 \| bar(1, 2, 3); \| ^^^^^^^ expected 2 parameters ``` 2017-03-29 01:56:29 +00:00			`}`