Allow complex length check conditions to determine the slice being nonnil #348
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.
We can have different length checks in Go code i.e.,
0 < len(a) - 1
instead of simply0 < len(a)
which would imply thata
is nonnil. However, NilAway currently only reasons about simple cases like0 < len(a)
. This PR adds the ability to reason about complex length check conditions by traversing the AST node and extracting thelen(a)
node.Note that we maintain an unsound assumption that the length check yields nonnil
a
(unless explicitly checking forlen(a) == 0
) to reduce false positives.Fixes #346