-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Move mismatch of Range#cover? and Range#include? out of shared folder #1053
Merged
+8
−1
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!
There is a missing
should
so no check actually performed.But titles of the proposed new cases for
include?
/cover?
don't describe their behaviour precisely.The
#cover?
method returns true because it compares begin/end and value with<=>
(or<
,>
) methods and indeed"\u{999}"
<"\u{9995}"
<"\u{9999}"
.But
#include?
for non-ascii String begin/end uses the#succ
method (that seems alphabetic-aware) and iterates from begin to end with#succ
looking for a value. But"\u{9999}"
and even"\u{9995}"
isn't reachable from"\u{999}"
- the largest reachable symbol is"\u{9b6}"
(I suppose because"\u{999}"
and"\u{9995}"
belong to different alphabets). I assume#succ
and consequently#include?
should work well with characters of the same alphabet only.So I would suggest changing titles of the new cases to describe the methods behaviour better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the descriptions. The inner encoding noob inside of me thinks they are correct now, so check them again please ;)