Repository navigation
test: harden coverage of numeric/range helpers past the 100% knife-edge - #551
Merged
Merged
Conversation
The merged coverage gate sat on the 99.94% rounding boundary: complexEqual (80%), rationalEqual (83%), rangeInts (80%), rangeSize (78%) and rangeElems (93%) had branches the operator/opcode paths never exercised, so a PR adding any code could tip the -race total below 100.0% on the POSIX lanes even with its own additions fully covered. Drive those five helpers through every branch (Complex/Rational == against Complex/Rational/Float/real/non-numeric; Range size/elems across inclusive, exclusive, empty, String and the non-integer TypeError) via a whitebox internal test plus MRI-checked eval cases. The merged total is now 100.0% with margin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The merged coverage gate sat on the ~99.94% rounding boundary — complexEqual, rationalEqual, rangeInts, rangeSize, rangeElems had branches the operator/opcode paths never hit, so any PR adding code could tip the -race POSIX total below 100.0% even with its own additions fully covered (this repeatedly failed #549 despite its functions all being 100%). This drives those five helpers through every branch via a whitebox internal test + MRI-checked eval cases. Merged total is now 100.0% with margin, so the strict gate stops flaking.
🤖 Generated with Claude Code