SILGen: Fix invalid SIL emitted when protocol requirement witnessed by base class convenience init [4.2] #16900
Conversation
This file contains hidden or 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
…y base class convenience init If the derived class is final and the base class is not, the protocol requirement can be witnessed by a non-required initializer. Non-required initializers have initializing but not allocating entry points in the vtable. The fix here statically dispatches to the allocating initializer instead. The test verifies that the allocating entry point uses alloc_ref_dynamic, so you will get an instance of the correct subclass. This fix does not handle the resilient case where the conformance is defined in a different module, and the original module adds an override of the convenience init later. I filed <rdar://problem/40639124> to track the resilient case. Fixes <rdar://problem/40003840>.
|
@swift-ci Please test |
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.
If the derived class is final and the base class is not, the
protocol requirement can be witnessed by a non-required
initializer. Non-required initializers have initializing
but not allocating entry points in the vtable.
The fix here statically dispatches to the allocating
initializer instead. The test verifies that the allocating
entry point uses alloc_ref_dynamic, so you will get an
instance of the correct subclass.
This fix does not handle the resilient case where the
conformance is defined in a different module, and the original
module adds an override of the convenience init later.
I filed rdar://problem/40639124 to track the resilient case.
Fixes rdar://problem/40003840.