Skip to content

[5.7][lldb] Look through existential types when handling typealiases in SwiftASTContext to correctly handle AnyObject existentials.#4863

Merged
hborla merged 1 commit intoswiftlang:swift/release/5.7from
hborla:5.7-lldb-existential-any-anyobject
Jun 24, 2022
Merged

[5.7][lldb] Look through existential types when handling typealiases in SwiftASTContext to correctly handle AnyObject existentials.#4863
hborla merged 1 commit intoswiftlang:swift/release/5.7from
hborla:5.7-lldb-existential-any-anyobject

Conversation

@hborla
Copy link
Copy Markdown
Member

@hborla hborla commented Jun 23, 2022

This is #4852, against the right branch this time 🙂

swiftlang/swift#59657 updates the representation of Any and AnyObject in the Swift frontend to use ExistentialType. Typealiases like AnyObject can be used as existential types, which are represented as ExistentialType(TypeAliasType), so LLDB should look through to an existential type's constraint when checking whether it has a typealias.

@hborla hborla requested a review from adrian-prantl June 23, 2022 00:47
@hborla
Copy link
Copy Markdown
Member Author

hborla commented Jun 23, 2022

swiftlang/swift#59657

@swift-ci please test

@hborla hborla force-pushed the 5.7-lldb-existential-any-anyobject branch from 0cacfc6 to adedc74 Compare June 24, 2022 04:19
@hborla
Copy link
Copy Markdown
Member Author

hborla commented Jun 24, 2022

@swift-ci please test

SwiftASTContext to correctly handle AnyObject existentials.
@hborla hborla force-pushed the 5.7-lldb-existential-any-anyobject branch from adedc74 to ccb4a75 Compare June 24, 2022 19:27
@hborla
Copy link
Copy Markdown
Member Author

hborla commented Jun 24, 2022

@swift-ci please test

@hborla hborla merged commit 5dfda22 into swiftlang:swift/release/5.7 Jun 24, 2022
@hborla hborla deleted the 5.7-lldb-existential-any-anyobject branch June 24, 2022 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants