Skip to content
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

Lint/BinaryOperatorWithIdenticalOperands raises error following merge of #8478 #8534

Closed
fran-worley opened this issue Aug 13, 2020 · 1 comment
Assignees

Comments

@fran-worley
Copy link

Following updating to rubocop 0.89.1, we are getting an error when passing one of our files. I suspect something in #8478 has caused the issue as the line in question includes a *.


Expected behavior

Run lint without errors

Actual behavior

When running the lint, the following message appeared

1 error occurred:
An error occurred while Lint/BinaryOperatorWithIdenticalOperands cop was inspecting /path_to_file/expire.rb:74:44.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.89.1 (using Parser 2.7.1.4, rubocop-ast 0.3.0, running on ruby 2.6.5 x86_64-darwin18)

Steps to reproduce the problem

The line which triggers the error includes the following Sequel.function(:count).*
While a little unusual, it is valid Ruby and a necessary part of the Sequel gem see docs

RuboCop version

$ bundle exec rubocop -V
0.89.1 (using Parser 2.7.1.4, rubocop-ast 0.3.0, running on ruby 2.6.5 x86_64-darwin18)
@marcandre
Copy link
Contributor

OMG, I never thought of using these operators like that, kind of cute and kind of horrific 😆

That's my bad I think, I'll fix this, sorry for the trouble.

@marcandre marcandre self-assigned this Aug 13, 2020
marcandre added a commit to marcandre/rubocop that referenced this issue Aug 13, 2020
…or binary operators used as unary operators
@mergify mergify bot closed this as completed in 8661e99 Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants