We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
<=>
<⇒
This bug is with the documentation for, so I've opted not to use the template, as it doesn't really make sense.
In the documentation for Performance/RedundantSortBlock, the following snippet
Performance/RedundantSortBlock
Identifies places where sort { |a, b| a <=> b } can be replaced with sort.
sort { |a, b| a <=> b }
sort
is incorrectly rendered as a partial ligature
Identifies places where sort { |a, b| a <⇒ b } can be replaced with sort.
sort { |a, b| a <⇒ b }
-sort { |a, b| a <=> b } +sort { |a, b| a <⇒ b }
The documentation comment in the source code from which this is generated is correct.
# Identifies places where `sort { |a, b| a <=> b }` can be replaced with `sort`.
I have not checked for other occurrences, or if this affects cops outside rubocop-performance.
rubocop-performance
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This bug is with the documentation for, so I've opted not to use the template, as it doesn't really make sense.
In the documentation for
Performance/RedundantSortBlock
, the following snippetis incorrectly rendered as a partial ligature
The documentation comment in the source code from which this is generated is correct.
# Identifies places where `sort { |a, b| a <=> b }` can be replaced with `sort`.
I have not checked for other occurrences, or if this affects cops outside
rubocop-performance
.The text was updated successfully, but these errors were encountered: