Skip to content

[5.1][TypeChecker] Don't try to validate generic requirements when unbound… #25223

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 3, 2019

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jun 3, 2019

… generic types are involved

If one of the generic parameters is missing let's give solver a
chance to diagnose the problem, otherwise there is a risk of failing
type resolution and not producing any diagnostics.

Reviewed by: @slavapestov

Resolves: rdar://problem/50099849
(cherry picked from commit 6b35f5d)

… generic types are involved

If one of the generic parameters is missing let's give solver a
chance to diagnose the problem, otherwise there is a risk of failing
type resolution and not producing any diagnostics.

Resolves: rdar://problem/50099849
(cherry picked from commit 6b35f5d)
@xedin
Copy link
Contributor Author

xedin commented Jun 3, 2019

@swift-ci please test

@xedin xedin merged commit 5e08867 into swiftlang:swift-5.1-branch Jun 3, 2019
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.

1 participant