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.
Improve
lenstringzeroprecision forlen(string)aliases in zero-comparisons #37750New 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
Uh oh!
There was an error while loading. Please reload this page.
Improve
lenstringzeroprecision forlen(string)aliases in zero-comparisons #37750Changes from all commits
154d3730ac57f2c74368a52af095File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnose] Compound-assignment operators (
+=,-=,*=,/=,%=, ...) are not invalidated — this causes false positives.stmt.Tokforn += 1istoken.ADD_ASSIGN, which falls through theswitch stmt.Tokwithout callingdelete(aliases, obj). The alias stays in the map, so the subsequentn == 0is reported even thoughnno longer holdslen(s).💡 Suggested fix — fold ASSIGN into default
Change the
switchto adefaultcase; any non-DEFINEtoken (plain=,+=,-=, ...) should invalidate the alias:A failing regression fixture to add in the test data:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The flipped alias forms
0 == nand0 != nare handled by the code (theisIntZero(expr.X)branch inrun()) but have no test fixtures.All four direct-
lenflipped forms have fixtures (flippedEmpty,flippedNotEmpty); the alias path deserves parity so a future refactor cannot silently drop that branch.💡 Suggested fixtures to add after this function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] No negative test for compound-assignment mutations (
+=,-=, etc.).aliasIncrementedNotFlaggedcoversn++(an*ast.IncDecStmt), but compound assignments are a distinct AST node (*ast.AssignStmtwith a non-=/:=token) and currently trigger a false positive (the alias is not invalidated). A fixture here would serve as a regression anchor once the bug incollectLenStringAliasesFromAssignStmtis fixed.💡 Suggested fixture
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd]
collectLenStringAliasesFromValueSpec(thevar n = len(s)path) has no test coverage.The
ValueSpechandler runs forvardeclarations inside functions, but no fixture exercises this code path. It is functionally symmetric to:=and is worth pinning with a positive case.💡 Suggested fixture
Uh oh!
There was an error while loading. Please reload this page.