diff options
| author | Jubilee <46493976+workingjubilee@users.noreply.github.com> | 2023-12-09 00:48:11 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-09 00:48:11 -0800 |
| commit | 61dfb1f8d07ed71e2515e641017118f12805882a (patch) | |
| tree | eb74168f86dbfe8b810adc14f629425f4e529bae /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 402cfb17f76e54392b2e12ebfe89bf5bbae08228 (diff) | |
| parent | e9878125216e660601182dcadbc1c86910333a64 (diff) | |
| download | rust-61dfb1f8d07ed71e2515e641017118f12805882a.tar.gz rust-61dfb1f8d07ed71e2515e641017118f12805882a.zip | |
Rollup merge of #118764 - compiler-errors:fused-async-iterator, r=eholk
Make async generators fused by default I actually changed my mind about this since the implementation PR landed. I think it's beneficial for `async gen` blocks to be "fused" by default -- i.e., for them to repeatedly return `Poll::Ready(None)` -- rather than panic. We have [`FusedStream`](https://docs.rs/futures/latest/futures/stream/trait.FusedStream.html) in futures-rs to represent streams with this capability already anyways. r? eholk cc ```@rust-lang/wg-async,``` would like to know if anyone else has opinions about this.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions