-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Retire Performance/ArraySemiInfiniteRangeSlice
cop
#198
Comments
What is the process to retire cops here? Do we just disable the cop from |
I don't know tbh. I note that these constants are not frozen 😈 I imagine that disabling it by default and commenting in the doc is the way to go... |
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This cop was created due to a mistake in microbenchmark Refer rubocop#175 (comment) Closes rubocop#197, rubocop#198
This can be closed via #199 |
I'd like to plan to remove this cop in the future RuboCop Performance 2.0. And any approach that does not cause breaking change needs to be considered. I will leave this issue until then. |
I opened an issue on RuboCop's side for this. |
This cop was created due to a mistake in the microbenchmark.
I would like to repeat: if there is no fundamental reason why something is slower, then... it might not be, or there might be a bug.
The text was updated successfully, but these errors were encountered: