E0593 could suggest using tuple as closure arg

[matthiaskrgr]

Code

` stderr.lines().enumerate().find(|i, line| line == ice_msg)`

Current output

Checking icemaker v0.1.0 (/home/matthias/vcs/github/icemaker_tree_update/icemaker)
error[E0593]: closure is expected to take 1 argument, but it takes 2 arguments
    --> src/main.rs:1082:44
     |
1082 |                 stderr.lines().enumerate().find(|i, line| line == ice_msg)
     |                                            ^^^^ --------- takes 2 arguments
     |                                            |
     |                                            expected closure that takes 1 argument

For more information about this error, try `rustc --explain E0593`.

Desired output

something like help/hint:
wrap the closure args in a tuple

1082 |                 stderr.lines().enumerate().find(|(i, line)| line == ice_msg)
     | +                                               -+-------+- warp closure args in a tuple

Rationale and extra context

No response

Other cases

No response

Rust Version

rustc 1.79.0-nightly (a07f3eb43 2024-04-11)
binary: rustc
commit-hash: a07f3eb43acc5df851e15176c7081a900a30a4d7
commit-date: 2024-04-11
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly

Anything else?

No response

[eggyal]

I wonder what the conditions for this should be?

• only suggest if the closure is expected to take one argument but actually takes more than one? (E0593)
• only suggest if the closure is expected to take one tuple argument but actually takes more than one?
• only suggest if the closure is expected to take one n-tuple argument but actually takes n?
• only suggest if the closure is expected to take (A, B, ..) argument but actually takes A, B, ..? (might not play well with inference)

Obviously none of these would help with closures that are expected to take multiple arguments, eg a tuple and something else, but it could get exponentially more difficult to identify a sensible suggestion in such cases.