[6.3] SILGen: Fix edge case where we didn't erase opaque result type in constructor #86169
+57
−1
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.
6.3 cherry-pick of #86168.
Description: Fix a SILGen or IRGen (depending on asserts on/off) crash when emitting an allocating initializer when the type of
selfcontains an opaque result type that can be erased.Origination: Never worked.
Issues: Compiler Crash When Using an Opaque Type in a Conditional Extension #68298, Use of opaque type to fulfill associated type requirement can cause a compiler crash. #68277.
Reviewed by: @DougGregor
Risk: Very low.