Keep obj node for struct ArrayIndex. #54584
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.
That was the last IND node on the LHS of a struct assignment without structHandle/known size.
There are small regressions because we now create
NULLCHECK
nodes where before we were keepingADDR(IND
that rationalizer was destroying.Edited: The diffs are small and they are minopts only (don't create INDEX_ADDR in other cases, thanks @erozenfeld). The issue is similar to #44087 but because it minopts we won't delete the extra node even when the issue is fixed.