diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-22 15:28:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-22 15:28:41 +0200 |
| commit | 457087ed29162978f150b434ca000c4c7274de0d (patch) | |
| tree | eed8d31c9ed4949642a592d3f3e461e03676ba2e /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 3f15d296f4de1db28dabdeec6a25d90f40d1dcff (diff) | |
| parent | c8b71ef3dd83f1d6b99d128ff2fc3b99c9ce28ab (diff) | |
| download | rust-457087ed29162978f150b434ca000c4c7274de0d.tar.gz rust-457087ed29162978f150b434ca000c4c7274de0d.zip | |
Rollup merge of #131549 - compiler-errors:try-in-sync, r=spastorino
Add a note for `?` on a `impl Future<Output = Result<..>>` in sync function It's confusing to `?` a future of a result in a sync function. We have a suggestion to `.await` it if we're in an async function, but not a sync function. Note that this is the case for sync functions, at least. Let's be a bit more vague about a fix, since it's somewhat context dependent. For example, you could block on it, or you could make your function asynchronous. 🤷
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
