Use Ruby 3.3 Range#overlap?
if available
#49317
Merged
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.
Motivation / Background
This commit uses Ruby 3.3
Range#overlap?
that has been added to Ruby via ruby/ruby#8242 . Rails 7.1 renamesRange#overlaps?
toRange#overlap?
via #48565 , This commit is not feasible to backport because there is noRange#overlap?
in Rails 7.0.zDetail
This commit addresses the CI faiilure at https://buildkite.com/rails/rails/builds/99745#018a9ea8-82f0-40a6-90c3-cdaa6dabebab/1092-1095 because without this commit, it shows
warning: method redefined; discarding old overlap?
.Additional information
None
Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]