Fix a crash when a protocol with a default implementation is aliased with the same name #534
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.
Bug/issue #, if applicable: rdar://107623749
Summary
Fix a crash (from a
fatalError
inDocumentationContext
) when a protocol with a default implementation in one module is both@_export
imported and type aliased in another module.Dependencies
None
Testing
@_exported import
to bring the symbols of the "Inner" target into the "Outer" target and also create a typealias with the same name as protocol from the "Inner" targetChecklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
./bin/test
script and it succeeded