Member expression bounds checking in multiple assignments #1181
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 PR fixes an issue with bounds checking member expressions across multiple assignments.
Consider an example:
After the assignment
s->p = arr
, the observed bounds ofs->p
arebounds(arr, arr + 3)
. At the assignments->len = 3
, we synthesize the member expressions->p
whose target boundsbounds(s->p, s->p + s->len)
use the value ofs->len
. However, sinces->p
already has observed bounds recorded inState.ObservedBounds
, we do not update the observed bounds ofs->p
to its target bounds. Therefore, the assignment tos->len
does not modify the observed bounds ofs->p
. At the end of this statement, the observed bounds ofs->p
arebounds(arr, arr + 3)
and we have equality betweens->p
andarr
and betweens->len
and3
. The observed boundsbounds(arr, arr + 3)
imply the target boundsbounds(s->p, s->p + s->len)
. No errors or warnings are emitted.