rust/tests/ui/argument-suggestions/issue-96638.stderr

error[E0061]: this function takes 3 arguments but 2 arguments were supplied
  --> $DIR/issue-96638.rs:8:5
   |
LL |     f(&x, "");
   |     ^ --  -- expected `usize`, found `&str`
   |       |
   |       argument #1 of type `usize` is missing
   |
note: function defined here
  --> $DIR/issue-96638.rs:1:4
   |
LL | fn f(_: usize, _: &usize, _: usize) {}
   |    ^ --------             --------
help: provide the argument
   |
LL -     f(&x, "");
LL +     f(/* usize */, &x, /* usize */);
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0061`.
Mitigate impact of subtle invalid call suggestion logic There's some subtle interaction between inferred expressions being passed as an argument to fn calls with fewer than expected arguments. To avoid the ICE, I'm changing indexing operations with `.get(idx)`, but the underlying logic still needs to be audited as it was written with the assumption that `final_arg_types` and `provided_args` have the right length. Address 96638. 2022-05-02 19:11:03 +00:00			`error[E0061]: this function takes 3 arguments but 2 arguments were supplied`
			`--> $DIR/issue-96638.rs:8:5`
			`\|`
			`LL \| f(&x, "");`
Label argument coercion errors 2022-08-13 05:22:47 +00:00			\| ^ -- -- expected `usize`, found `&str`
			`\| \|`
Use ordinal number in argument error Fix error message Fix tests Format 2024-05-12 16:40:59 +09:00			\| argument #1 of type `usize` is missing
Mitigate impact of subtle invalid call suggestion logic There's some subtle interaction between inferred expressions being passed as an argument to fn calls with fewer than expected arguments. To avoid the ICE, I'm changing indexing operations with `.get(idx)`, but the underlying logic still needs to be audited as it was written with the assumption that `final_arg_types` and `provided_args` have the right length. Address 96638. 2022-05-02 19:11:03 +00:00			`\|`
			`note: function defined here`
			`--> $DIR/issue-96638.rs:1:4`
			`\|`
			`LL \| fn f(_: usize, _: &usize, _: usize) {}`
When displaying a parameter mismatch error, only highlight the mismatched parameters when showing the definition. 2025-02-05 09:28:35 -05:00			`\| ^ -------- --------`
Mitigate impact of subtle invalid call suggestion logic There's some subtle interaction between inferred expressions being passed as an argument to fn calls with fewer than expected arguments. To avoid the ICE, I'm changing indexing operations with `.get(idx)`, but the underlying logic still needs to be audited as it was written with the assumption that `final_arg_types` and `provided_args` have the right length. Address 96638. 2022-05-02 19:11:03 +00:00			`help: provide the argument`
			`\|`
Show diff suggestion format on verbose replacement ``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 \| LL \| let _ = 2.l; \| ^ \| help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix \| LL - let _ = 2.l; LL + let _ = 2.0f64; \| ``` 2024-07-09 22:30:26 +00:00			`LL - f(&x, "");`
			`LL + f(/* usize /, &x, / usize */);`
			`\|`
Mitigate impact of subtle invalid call suggestion logic There's some subtle interaction between inferred expressions being passed as an argument to fn calls with fewer than expected arguments. To avoid the ICE, I'm changing indexing operations with `.get(idx)`, but the underlying logic still needs to be audited as it was written with the assumption that `final_arg_types` and `provided_args` have the right length. Address 96638. 2022-05-02 19:11:03 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Mitigate impact of subtle invalid call suggestion logic There's some subtle interaction between inferred expressions being passed as an argument to fn calls with fewer than expected arguments. To avoid the ICE, I'm changing indexing operations with `.get(idx)`, but the underlying logic still needs to be audited as it was written with the assumption that `final_arg_types` and `provided_args` have the right length. Address 96638. 2022-05-02 19:11:03 +00:00
			For more information about this error, try `rustc --explain E0061`.