Skip to content

[pull] swiftwasm from swift/main #1102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 3, 2021
Merged

[pull] swiftwasm from swift/main #1102

merged 4 commits into from
Feb 3, 2021

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 3, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

adrian-prantl and others added 4 commits February 2, 2021 11:04
Foundation, for example, generates new Objective-C classes on the fly
(such as instances of _DictionaryStorage<T1, T2>) and LLDB's ObjC
runtime implementation isn't set up to recognize these. As a
workaround, this patch tries to resolve (id) types in Swift as Swift
types when doing dynamic type resolution.

rdar://73216083+73842894
(cherry picked from commit 9c31e14)
…tside of types log)

The LogConfiguration() output is especially interesting if things
aren't going as planned, so let's invoke it on all early exists as
well.

rdar://70008042
(cherry picked from commit dec585e)
@pull pull bot merged commit 0a69ba7 into swiftwasm Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant