Skip to content

[Serialization] Recover from deserialization failures in ModuleFile::lookupClassMembers #38046

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 1 commit into from
Jun 23, 2021

Conversation

xymus
Copy link
Contributor

@xymus xymus commented Jun 23, 2021

Code attempting to access a missing member on an AnyObject triggers a typo correction that deserializes all class members in imported modules, even non-public ones. This change makes sure the compiler recovers from deserializing class members referencing implementation-only imported types.

rdar://79427805

Access to a missing member on an AnyObject triggers a typo correction
that looks at all class members in imported modules. Make sure it
recovers from deserializing members referencing implementation-only
imported types.

rdar://79427805
@xymus xymus requested review from bnbarham and artemcm June 23, 2021 01:39
@xymus
Copy link
Contributor Author

xymus commented Jun 23, 2021

@swift-ci Please smoke test

@xymus
Copy link
Contributor Author

xymus commented Jun 23, 2021

@swift-ci Please test Windows platform

@xymus
Copy link
Contributor Author

xymus commented Jun 23, 2021

@swift-ci Please smoke test macOS

@xymus
Copy link
Contributor Author

xymus commented Jun 23, 2021

@swift-ci Please test Windows platform

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.

3 participants