rust/compiler/rustc_middle
许杰友 Jieyou Xu (Joe) aae4730c78
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
2024-10-18 12:00:51 +01:00
..
src Rollup merge of #131802 - compiler-errors:fnonce-coverage, r=Zalathar 2024-10-18 12:00:51 +01:00
Cargo.toml compiler: Factor rustc_target::abi::* out of middle::ty::layout 2024-10-08 18:14:48 -07:00
messages.ftl TL note: current means target 2024-09-20 10:02:14 -07:00
README.md

For more information about how rustc works, see the rustc dev guide.