diff options
| author | Zalathar <Zalathar@users.noreply.github.com> | 2024-03-20 18:17:23 +1100 |
|---|---|---|
| committer | Zalathar <Zalathar@users.noreply.github.com> | 2024-03-20 18:22:15 +1100 |
| commit | 85bec7a50c9a8ab466f8fbafa7b0c4eb05e6c721 (patch) | |
| tree | 754ed4c50f83d34f6b3461b957f276ca7ea55b2b /tests/coverage/let_else_loop.coverage | |
| parent | 70206f06ca5cff08d3b84240074ec89e705ab61b (diff) | |
coverage: Remove incorrect assertions from counter allocation
These assertions detect situations where a BCB node would have both a physical counter and one or more in-edge counters/expressions. For most BCBs that situation would indicate an implementation bug. However, it's perfectly fine in the case of a BCB having an edge that loops back to itself. Given the complexity and risk involved in fixing the assertions, and the fact that nothing relies on them actually being true, this patch just removes them instead.
Diffstat (limited to 'tests/coverage/let_else_loop.coverage')
| -rw-r--r-- | tests/coverage/let_else_loop.coverage | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/coverage/let_else_loop.coverage b/tests/coverage/let_else_loop.coverage index 3b3c39ff301..d193c8ca1b5 100644 --- a/tests/coverage/let_else_loop.coverage +++ b/tests/coverage/let_else_loop.coverage @@ -1,6 +1,6 @@ LL| |#![feature(coverage_attribute)] LL| |//@ edition: 2021 - LL| |//@ ignore-test + LL| | LL| |// Regression test for <https://github.com/rust-lang/rust/issues/122738>. LL| |// These code patterns should not trigger an ICE when allocating a physical LL| |// counter to a node and also one of its in-edges, because that is allowed |