Specify compile-time evaluation of field and index accesses #1329
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 adds to the list of (local) compile-time known values in section 18.1. (#1323)
In summary, for index access,
e1[e2]
is local compile-time known if bothe1
ande2
are local compile-time known.e1[e2]
is compile-time known if bothe1
ande2
are compile-time known.e1
should be of a header stack or tuple type.And for field access,
e.x
is local compile-time known ife
is local compile-time known.e.x
is compile-time known ife
is compile-time known.e
should be of a struct, header, or header union type.