Fix: no-extra-parens reported some parenthesized IIFEs (fixes #9140) #9158
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.
What is the purpose of this pull request? (put an "X" next to item)
[x] Bug fix (#9140)
What changes did you make? (Give an overview)
This updates
no-extra-parens
to handle IIFEs more consistently by doing an IIFE check as part of thereport
call, rather than overloading the precedence calculation with special logic for IIFEs.The bug occurred because the rule was assuming that the precedence calculation would always return -1 for an IIFE, preventing it from ever being reported (since any surrounding parens would always be considered necessary). However, the
ReturnStatement
listener doesn't check the precedence of its argument (since it correctly assumes thatreturn
statements have the lowest precedence), so it incorrectly caused the IIFE to be reported.Is there anything you'd like reviewers to focus on?
Nothing in particular