Re: [PATCH] rust: clean Rust 1.86.0 new `clippy::needless_continue` cases
From: Benno Lossin
Date: Tue Apr 01 2025 - 19:53:26 EST
On Wed Apr 2, 2025 at 12:12 AM CEST, Miguel Ojeda wrote:
> Starting with the upcoming Rust 1.86.0, Clippy's `needless_continue` lint
> complains about the last statement of a loop [1], including cases like:
>
> while ... {
> match ... {
> ... if ... => {
> ...
> return ...;
> }
> _ => continue,
> }
> }
>
> as well as nested `match`es in a loop.
>
> Thus clean them up.
>
> Link: https://github.com/rust-lang/rust-clippy/pull/13891 [1]
> Signed-off-by: Miguel Ojeda <ojeda@xxxxxxxxxx>
> ---
> To be honest, I am not sure we want this.
>
> The lint can find cases that should be simplified, and it has been a nice lint
> so far, but somehow I feel that using `continue` shows the intent better when
> it is alone in an arm like that, and I am not sure we want to force people to
> try to find other ways to write the code either, in cases when that applies.
>
> If others feel this reads worse, then I would be happy to disable the lint and
> open an issue upstream to keep the cases that are more clear cut.
I'm not too sure about this change, if the loop is longer than one
screen, it makes a lot of sense to have a `continue` instead of `()`,
since one might not see that there is nothing after the `match`.
I also think that an explicit `continue` is nicer from a expressability
standpoint. So I think we should keep them.
---
Cheers,
Benno
> rust/macros/helpers.rs | 2 +-
> rust/macros/kunit.rs | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)