Fix erasure crash for Inlined rhs of a context function closure #20398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is achieved by safely removing Inlined nodes at that point, in the same manner they would be removed later in `typedInlined`` in the same phase.
hamzaremmal
approved these changes
May 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #16963
The regression here was caused by 229fdaa, by the changes to TreeInfo. Since the aim of that PR was to reduce unnecessary
Inlinedremoval, instead of reintroducingInlinednode removal inclosureDefinTreeInfo(which is used in many places in the compiler), we just remove it directly in erasure, where it would have been removed later in the same manner either way (intypedInlined).