Fix bugzilla 24845 - Compiler error when trying to assign to an AA va… #17094
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.
…lue of an enum instance
There used to be a special case that indexing an associative array literal results in an rvalue, but any other result of indexing an AA rvalue is still an lvalue. This PR gives AA's the same rules as static arrays: the indexed value is an lvalue iff the array is an lvalue. This is different from dynamic arrays, where
&[x][0]
is allowed.Targeting master because this could break code that relied on
makeAA()["key"] = 0
compiling.