Swift: Update swift/string-length-conflation to taint tracking#12307
Merged
Conversation
…move a special case that's now covered by taint.
jketema
approved these changes
Mar 2, 2023
Contributor
jketema
left a comment
jketema
left a comment
There was a problem hiding this comment.
Should we run DCA on this? Otherwise LGTM.
Contributor
Author
Yep, that's probably a good idea... |
Contributor
Author
|
DCA completed and LGTM. Merging... |
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
2 participants
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.
Update
swift/string-length-conflationto taint tracking, so that it benefits from flow through arithmetic operations without special cases (now that taint does indeed support these cases). This may introduce new (hopefully good) results, though it doesn't in the MRVA top 100 so I think this will be rare.