allow variable access on constant/literal arrays #2534
Merged
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.
What I did
Fix #2156 and #2130
Note that a bug similar to #2130 can still be triggered with a list of ambiguous type. For instance,
MY_LIST: constant(uint256[1]) = [1]
. I used adecimal
in the test to demonstrate that the array literals pass but the type checker issue still needs to be addressed.How I did it
Expand the logic in
Expr.parse_Subscript
to handle constants/literalsHow to verify it
See test
Description for the changelog
Allow variable access on constant/literal arrays
Cute Animal Picture