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: Clean up terminology in counter creation #130184

Merged
merged 3 commits into from
Sep 10, 2024

Commits on Sep 10, 2024

  1. coverage: Avoid referring to "coverage spans" in counter creation

    The counter-creation code needs to know which BCB nodes require counters, but
    isn't interested in why, so treat that as an opaque detail.
    Zalathar committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    96d545a View commit details
    Browse the repository at this point in the history
  2. coverage: Avoid referring to out-edges as "branches"

    This makes the graph terminology a bit more consistent, and avoids potential
    confusion with branch coverage.
    Zalathar committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    8be70c7 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    10cd5e8 View commit details
    Browse the repository at this point in the history