[refurb
] Correctly handle lengths of literal strings in slice-to-remove-prefix-or-suffix
(FURB188
)
#16237
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.
Fixes false negative when slice bound uses length of string literal.
We were meant to check the following, for example. Given:
We want to know whether:
suffix
is a string literal andbound
is a number literalsuffix
is an expression andbound
isexactly
-len(suffix)
(as AST nodes, prior to evaluation.)The issue is that negative number literals like
-10
are stored as unary operators applied to a number literal in the AST. So whensuffix
was a string literal butbound
was-len(suffix)
we were getting caught in the match arm wherebound
needed to be a number. This is now fixed with a guard.Closes #16231