Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coverage: Treat each match arm as a "branch" for branch coverage #124154

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Commits on Jun 26, 2024

  1. Configuration menu
    Copy the full SHA
    b71dcdb View commit details
    Browse the repository at this point in the history
  2. coverage: Represent branches as a list of arms

    Within the `InstrumentCoverage` pass, we now represent branches as a list of
    arms, instead of a true/false pair, until we prepare the final table of
    mappings to be attached to the MIR body.
    
    (We then flatten the list into two-way branches by treating each arm as a
    branch between its success block, and the total of all later arms.)
    
    Currently all of the branches produced by MIR building are still two-way, but
    this is a step towards allowing many-way branches.
    Zalathar committed Jun 26, 2024
    Configuration menu
    Copy the full SHA
    79e5b4f View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    a513c92 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    5959561 View commit details
    Browse the repository at this point in the history