unnecessary_move lint, removing move with no effect

What it does

clippy reports no warnings for unnecessary move keyword, such as:

let closure = move || value_moved(v);

Here move is unnecessary since there's no reference capture.

If a lint for above is acceptable, we may also have some warnings for belows.

std::thread::spawn(move || { value_moved(v) }

or

tokio::spawn(async move || value_moved_async(v).await})

Lint Name

unnecessary_move

Category

style

Advantage

• Brings minimalism.

Drawbacks

No response

Example

move || value_moved(v);

Could be written as:

|| value_moved(v);

No implementation file or test is named. First review existing Clippy lint implementations and tests for closure captures, then determine whether the proposed cases are valid and how the lint should handle closures passed to spawning APIs. Done means an accepted scope, diagnostics for the supported examples, and tests covering the chosen behavior.