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

Fix coverage for matches containing a single case. #626

Closed
wants to merge 1 commit into from

Conversation

rmn30
Copy link
Contributor

@rmn30 rmn30 commented Jul 8, 2024

The C backend tries not to emit branch coverage points for matches
containing a single case but was still emitting a line in
all_branches. This confused sailcov and resulting in warnings and
weird output. Hopefully fixes #502. Also adds a test case containing
a tuple deconstruction (which apparently gets compiled to a single
case match).

The C backend tries not to emit branch coverage points for matches
containing a single case but was still emitting a line in
all_branches.  This confused sailcov and resulting in warnings and
weird output.  Hopefully fixes #502.  Also adds a test case containing
a tuple deconstruction (which apparently gets compiled to a single
case match).
@rmn30 rmn30 requested a review from Alasdair July 8, 2024 14:02
@Alasdair
Copy link
Collaborator

Alasdair commented Jul 8, 2024

Ah, I think we simultaneously fixed the issue.

@rmn30 rmn30 closed this Jul 8, 2024
@rmn30
Copy link
Contributor Author

rmn30 commented Jul 8, 2024

Already fixed by 09ac4b2.

@rmn30 rmn30 deleted the coverage_match_fix branch July 8, 2024 14:09
@marnovandermaas
Copy link
Contributor

Thanks both for this fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sailcov fails upon goodness within badness
4 participants