Email me

Clippy lints / Correctness

Clippy lint · Correctness · checked with Clippy 0.1.99

clippy::async_yields_async: an async construct yields a type which is itself awaitable

What it meansChecks for async blocks that yield values of types that can themselves be awaited. It is in the correctness group and denied by default (the build fails).

What you see

error: an async construct yields a type which is itself awaitable
 --> main.rs:7:5
  |
6 |     let x = async {
  |  _________________-
7 | |     foo()
  | |     ^^^^^
  | |     |
  | |     awaitable value not awaited
  | |     help: consider awaiting this value: `foo().await`
8 | |   };
  | |___- outer async construct
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#async_yields_async
  = note: `#[deny(clippy::async_yields_async)]` 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?

An await is likely missing.

Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.

How to fix it

Clippy does not fix this one automatically (its suggestion may change behaviour, so it only shows it). Change the code by hand:

Flagged

async fn foo() {}

fn bar() {
  let x = async {
    foo()
  };
}

Write this instead

async fn foo() {}

fn bar() {
  let x = async {
    foo().await
  };
}

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::async_yields_async)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
async_yields_async = "allow"

One run

cargo clippy -- -A clippy::async-yields-async

The [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.

Correctnessgroup
denydefault level
nofixed by cargo clippy --fix
1.48.0added in Rust

Clippy's own documentation

What it does

Checks for async blocks that yield values of types that can themselves be awaited.

Why is this bad?

An await is likely missing.

Example

async fn foo() {}

fn bar() {
  let x = async {
    foo()
  };
}

Use instead:

async fn foo() {}

fn bar() {
  let x = async {
    foo().await
  };
}

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker

Up next

Related lintclippy::absurd_extreme_comparisonsthis comparison involving the minimum or maximum element for this type contains a case that is always true or always falseRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ