has_key?
description note is giving false impression
#595
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.
Hi
Currently in a section regarding
has_key?
vskey?
there is a sentence linking to an old email which was used as a rationale for this rule. It is also noted that thehas_key?
is considered deprecated.I believe that this note is unnecessary and can give a false impression.
has_key?
is not considered deprecated and is still actively in use. Matz clearly stated that it is not going anywhere here rubocop/rubocop#3224This makes me believe that the note about
has_key?
deprecation in Matz's mail was simply an unfortunately phrased opinion on a personal preference and is not an official statement of a core team.To back it up this rule started a discussion in my team today and this part of style guide was brought up as an argument while I firmly believe that choosing between
has_key?
andkey?
is highly subjective matter and one is arguably better than the other. This is especially true since the rationale behind this rule is no longer valid.Looks like my editor also fixed some trailing whitespaces ;)