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: Flatten the functions for extracting/refining coverage spans #120294

Closed
wants to merge 1 commit into from

Conversation

Zalathar
Copy link
Contributor

Consolidating this code into flatter functions reduces the amount of pointer-chasing required to read and modify it.

No functional changes.

Ignoring whitespace is recommended, as it shows that most of the moved code has not been modified.


This has a trivial conflict with #120292 (renamed function called by re-indented code), so when one merges, the other will require a tiny fixup.

@rustbot label +A-code-coverage

Consolidating this code into flatter functions reduces the amount of
pointer-chasing required to read and modify it.
@rustbot
Copy link
Collaborator

rustbot commented Jan 24, 2024

r? @b-naber

(rustbot has picked a reviewer for you, use r? to override)

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 24, 2024
@rustbot
Copy link
Collaborator

rustbot commented Jan 24, 2024

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbot rustbot added the A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) label Jan 24, 2024
@Zalathar
Copy link
Contributor Author

Hmm, I should probably just combine these two into one double-refactoring PR, to save the hassle of an extra conflict-resolution step.

@Zalathar Zalathar closed this Jan 24, 2024
@Zalathar Zalathar deleted the flatten branch February 2, 2024 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants