about summary refs log tree commit diff
path: root/tests/codegen/enum/enum-match.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-04-30 02:47:25 +0000
committerbors <bors@rust-lang.org>2024-04-30 02:47:25 +0000
commitf9dca46218d4b8efa062aec4fd0820cbb4942aa2 (patch)
treed618e09805a64c32ebc8868c917dd9ae9f746f29 /tests/codegen/enum/enum-match.rs
parent74a8df6c650f6067babf942a77f78e9b9a7fee31 (diff)
parentf9263374fb8143c7fa1850a43759249a73415cdf (diff)
downloadrust-f9dca46218d4b8efa062aec4fd0820cbb4942aa2.tar.gz
rust-f9dca46218d4b8efa062aec4fd0820cbb4942aa2.zip
Auto merge of #124507 - Zalathar:coverage-level, r=compiler-errors
coverage: Replace boolean options with a `CoverageLevel` enum

After #123409, and some discussion at https://github.com/rust-lang/rust/issues/79649#issuecomment-2042093553 and #124120, it became clear to me that we should have a unified concept of “coverage level”, instead of having several separate boolean flags that aren't actually independent.

This PR therefore introduces a `CoverageLevel` enum, to replace the existing boolean flags for `branch` and `mcdc`.

The `no-branch` value (for `-Zcoverage-options`) has been renamed to `block`, instructing the compiler to only instrument for block coverage, with no branch coverage or MD/DC instrumentation.

`@rustbot` label +A-code-coverage
cc `@ZhuUx` `@Lambdaris` `@RenjiSann`
Diffstat (limited to 'tests/codegen/enum/enum-match.rs')
0 files changed, 0 insertions, 0 deletions