Skip to content

AST: Fix excessive deserialization in GenericSignatureBuilder #7513

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

Conversation

slavapestov
Copy link
Contributor

When we're looking up all associated types with the same name in order
to find the right archetype anchor, skip extension members to avoid
circular deserialization.

Discovered while investigating rdar://problem/30248571.

When we're looking up all associated types with the same name in order
to find the right archetype anchor, skip extension members to avoid
circular deserialization.

Discovered while investigating <rdar://problem/30248571>.
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov slavapestov merged commit 010d2e8 into swiftlang:master Feb 16, 2017
@jrose-apple
Copy link
Contributor

I think we may be hitting the assert deterministically now! Baby steps. cc @DougGregor

@jrose-apple
Copy link
Contributor

I'm going to revert for now since hitting the assert more often means everyone is blocked. But it seems like it'll help us with tracking down the real error.

@DougGregor
Copy link
Member

My attempt at reinstating this is at #7530

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