[lldb] Teach LLDB about ExistentialType in the Swift AST.
#3777
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 was referenced Jan 12, 2022
|
@swift-ci please test |
|
@swift-ci please test macOS platform |
|
This PR was just for the purpose of cross-repo testing for swiftlang/swift#40666. My cherry-pick PR (#3778) will be auto merged from |
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.
swiftlang/swift#40282 adds a new type called
ExistentialTypeto the Swift frontend, and swiftlang/swift#40666 changes the representation of existential types to use this new type. This is currently semantically the same asProtocolTypeorProtocolCompositionType(the new type actually wraps one of these), so LLDB should handle the new type in the same way.