Fix unsed variable handling for update expressions - #274
Open
shin19991207 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Morgan Chang <shin19991207@gmail.com>
datho7561
force-pushed
the
fix-testUnusedVariableAsSwitchStatement
branch
from
May 7, 2026 20:43
196cc2b to
de3251b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixed javac unused-local analysis so update expressions are not count as meaningful variable reads.
Previously, an expression statement like
e += ""was treated as a read ofe.UnusedTreeScanneraddedetousedElementswhich caused the unused-local diagnostic to be skipped.This change handles compound assignments (
+=) and unary increment/decrement expressions (++,--) as writes only (usinglhsInAssignment), so they do not mark the variable as used.