Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::redundant_async_block: this async expression only awaits a single future
What it meansChecks for async block that only returns await on a future. It is in the complexity group and warns by default.
What you see
warning: this async expression only awaits a single future --> main.rs:6:11 | 6 | let fut = async { | ___________^ 7 | | f.await 8 | | }; | |_^ help: you can reduce it to: `f` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#redundant_async_block = note: `#[warn(clippy::redundant_async_block)]` on by default
Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.
Does it matter?
It is simpler and more efficient to use the future directly.
Code that does something simple in a complicated way. Warns by default.
How to fix it
Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Flagged
let f = async {
1 + 2
};
let fut = async {
f.await
};
Write this instead
let f = async {
1 + 2
};
let fut = f;
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::redundant_async_block)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
redundant_async_block = "allow"One run
cargo clippy -- -A clippy::redundant-async-blockThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Clippy's own documentation
What it does
Checks for async block that only returns await on a future.
Why is this bad?
It is simpler and more efficient to use the future directly.
Example
let f = async {
1 + 2
};
let fut = async {
f.await
};
Use instead:
let f = async {
1 + 2
};
let fut = f;
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_argumentsChecks for functions with too many parameters
- clone_on_copyusing `clone` on type `u64` which implements the `Copy` trait
- type_complexityChecks for types used in structs, parameters and let declarations above a certain complexity threshold
- ptr_offset_with_castuse of `offset` with a `usize` cast to an `isize`
- range_zip_with_lenChecks for zipping a collection with the range of 0.._.len()
- redundant_as_strChecks for usage of as_str() on a String chained with a method available on the String itself
- redundant_at_rest_patternusing a rest pattern to bind an entire slice to a local
- redundant_closure_calltry not to call a closure in the expression where it is declared
- redundant_guardsChecks for unnecessary guards in match expressions
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_argumentsChecks for functions with too many parametersRead it next →Did this answer your question?