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.

Sign up for GitHub

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

Jump to bottom

coverage: Separate initial span extraction from span processing #116409

Merged
merged 3 commits into from
Oct 10, 2023
Merged

coverage: Separate initial span extraction from span processing #116409

merged 3 commits into from
Oct 10, 2023

Commits on Oct 10, 2023

  1. coverage: Move initial MIR span extraction into a submodule

    @Zalathar
    Zalathar committed Oct 10, 2023
    Configuration menu
    Copy the full SHA
    972ab88 View commit details
    Browse the repository at this point in the history

  2. coverage: Disconnect span extraction from CoverageSpansGenerator 

    By performal initial span extraction in a separate free function, we can remove
some accidental complexity from the main generator code.
    @Zalathar
    Zalathar committed Oct 10, 2023
    Configuration menu
    Copy the full SHA
    4b471df View commit details
    Browse the repository at this point in the history

  3. coverage: Remove enum CoverageStatement 

    This enum was mainly needed to track the precise origin of a span in MIR, for
debug printing purposes. Since the old debug code was removed in rust-lang#115962, we
can replace it with just the span itself.
    @Zalathar
    Zalathar committed Oct 10, 2023
    Configuration menu
    Copy the full SHA
    6c44425 View commit details
    Browse the repository at this point in the history