diff options
| author | bors <bors@rust-lang.org> | 2023-05-26 00:30:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-26 00:30:24 +0000 |
| commit | 05740adf6ec2c79c9379e6f9ce804bd7b2567f57 (patch) | |
| tree | ae83e4043e6ea171b73570617e8621e9e4176174 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 9374af16abcd41162c9fddfb9c26c60879b87db5 (diff) | |
| parent | 8ef6240afb00ec9a892cb41c36cde102b688343a (diff) | |
| download | rust-05740adf6ec2c79c9379e6f9ce804bd7b2567f57.tar.gz rust-05740adf6ec2c79c9379e6f9ce804bd7b2567f57.zip | |
Auto merge of #10807 - y21:issue10800, r=Jarcho
[`unused_async`]: do not consider `await` in nested `async` blocks as used
Fixes #10800.
This PR makes sure that `await` expressions inside of inner `async` blocks don't prevent the lint from triggering.
For example
```rs
async fn foo() {
async {
std::future::ready(()).await;
}
}
```
Even though there *is* a `.await` expression in this function, it's contained in an async block, which means that the enclosing function doesn't need to be `async` too.
changelog: [`unused_async`]: do not consider `await` in nested `async` blocks as used
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions