diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2024-10-18 12:00:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-18 12:00:51 +0100 |
| commit | aae4730c78a966db79d5a76ad1a75c1429eb7f9a (patch) | |
| tree | b6986dd08fde0ebb44f923a44bfb110e69d11640 /compiler/rustc_codegen_llvm/src/llvm_util.rs | |
| parent | 951c0cd6f35381150b8f967b5e6d48c53c20100f (diff) | |
| parent | cdbf28af7694e0037d2ed8f78c40f60e5aef6de2 (diff) | |
| download | rust-aae4730c78a966db79d5a76ad1a75c1429eb7f9a.tar.gz rust-aae4730c78a966db79d5a76ad1a75c1429eb7f9a.zip | |
Rollup merge of #131802 - compiler-errors:fnonce-coverage, r=Zalathar
Dont ICE when computing coverage of synthetic async closure body I'm not totally certain if this is *right*, but at least it doesn't ICE. The issue is that we end up generating two MIR bodies for each async closure, since the `FnOnce` and `Fn`/`FnMut` implementations have different borrowing behavior of their captured variables. They should ideally both contribute to the coverage, since those MIR bodies are (*to the user*) the same code and should have no behavioral differences. This PR at least suppresses the ICEs, and then I guess worst case we can fix this the right way later. r? Zalathar or re-roll Fixes #131190
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm_util.rs')
0 files changed, 0 insertions, 0 deletions