Repository navigation
Add Range#overlap? - #468
Merged
Merged
Conversation
Range#overlap?(other) reports whether two ranges share at least one element, mirroring MRI's algorithm: the ranges are disjoint when one's end falls below the other's begin (touching ends count only when both are inclusive), and an empty range — backward, or begin equal to an exclusive end — overlaps nothing. A nil bound is an infinity; a non-Range argument raises TypeError. Verified against ruby 4.0.6. Whole-package coverage stays at 100%; the ruby/spec floor rises 15790 -> 15800 (core/range/overlap 0 -> 9). 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.
Range#overlap?(other)reports whether two ranges share at least one element,mirroring MRI's algorithm: the ranges are disjoint when one's end falls below the
other's begin (touching ends count only when both are inclusive), and an empty
range — backward, or begin equal to an exclusive end — overlaps nothing. A
nilbound is treated as an infinity; incomparable bounds report no overlap; and a
non-Range argument raises
TypeError.Verified against ruby 4.0.6. Whole-package coverage stays at 100%; the ruby/spec
ratchet floor rises 15790 → 15800 (
core/range/overlap0 → 9, zero regressionsin a deterministic per-file sweep).
🤖 Generated with Claude Code