Track usage of every assignment in UnusedLocalVariable #469
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.
This closes #458.
It was much more complex than I expected, but I think I've done. :)
UnusedLocalVariable
now tracks usage of every assignment, that is neither entire variable lifetime nor only last assignment.Before merging, I think we should consider reorganizing the new
UnusedLocalVariable
andUselessAssignment
.UnusedLocalVariable
is now superior toUselessAssignment
.UnusedLocalVariable
tracks every useless assignment in every scope.UselessAssignment
tracks useless assignment at the end of method.UselessAssignment
also tracks useless setter call at the end of method (technically it's not assignment though).I think there are two choices:
UselessAssignment
. Two different logics, the newUnusedLocalVariable
's one and the setter call tracking part of the currentUselessAssignment
, would live in a cop.UselessSetterCall
(or something), and renameUnusedLocalVariable
toUselessAssignment
.I'd prefer option 2.