Modernize respond_to implementations #264
Merged
Conversation
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
Since at least Ruby 1.8.7, `respond_to?` has supported an optional second parameter which causes private/protected methods to be included in the check. This defaults to false. As of Ruby 2, there's a warning logged if an implementation of `respond_to` does not take a second parameter, see: ruby/ruby@a106b31 This change updated the respond_to implementations to support the second parameter.
jnunemaker
pushed a commit
that referenced
this pull request
Jan 6, 2014
Modernize respond_to implementations
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.
Since at least Ruby 1.8.7,
respond_to?has supported an optionalsecond parameter which causes private/protected methods to be included
in the check. This defaults to false.
As of Ruby 2, there's a warning logged if an implementation of
respond_todoes not take a second parameter, see:ruby/ruby@a106b31
This change updated the respond_to implementations to support the second
parameter and squelch this warning.