Skip to content

Existentials don't always conform to a protocol via an abstract confo… #31736

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

aschwaighofer
Copy link
Contributor

…rmance

So it is not always correct to use the current conformance when substituting.

rdar://62894495

…rmance

So it is not always correct to use the current conformance when substituting.

rdar://62894495
@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test

@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test source compatibility

1 similar comment
@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test source compatibility

@aschwaighofer
Copy link
Contributor Author

@swift-ci please test source compatibility release

Copy link
Contributor

@slavapestov slavapestov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess the right long-term fix is to have opened archetypes store conformances or something like that.

@aschwaighofer
Copy link
Contributor Author

@swift-ci please test source compatibility release

@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test source compatibility release

@aschwaighofer aschwaighofer merged commit 5c4bbf3 into swiftlang:master May 13, 2020
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