[DOC] Tweaks for String#=~ #13325
Merged
[DOC] Tweaks for String#=~ #13325
Conversation
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
Comment on lines
-5334
to
-5335
| * If the given +object+ is not a Regexp, returns the value | ||
| * returned by <tt>object =~ self</tt>. |
There was a problem hiding this comment.
We lost this documentation for the case when regexp is not a regexp.
There was a problem hiding this comment.
See my recent comment below.
There was a problem hiding this comment.
You can just create your own object or use any non-string object that responds to #=~ (e.g. nil):
class Foo
def =~(other)
puts "calling =~ with #{other}"
123
end
end
p "hello" =~ Foo.new
# => calling =~ with hello
# => 123
p "hello" =~ nil
# => nil|
Noted in the OP:
|
peterzhu2118
approved these changes
May 15, 2025
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.
I could not find any non-Regexp +object+ that did not raise TypeError; are there any?