Skip to content

[CSDiag] Fix crash related to failures in contextual type requirements #20028

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 2 commits into from
Oct 25, 2018

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Oct 25, 2018

If failed constraint mentions member declaration which is not
generic, it means that generic requirements came from context
and should not be diagnosed by diagnoseUnresolvedDotExprTypeRequirementFailure.

Resolved: rdar://problem/45511837

@xedin xedin requested a review from nathawes October 25, 2018 00:26
@xedin
Copy link
Contributor Author

xedin commented Oct 25, 2018

@swift-ci please smoke test

Copy link
Contributor

@nathawes nathawes left a comment

Choose a reason for hiding this comment

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

Looks good, Pavel. Thanks!

xedin added 2 commits October 24, 2018 18:20
If failed constraint mentions member declaration which is not
generic, it means that generic requirements came from context
and should not be diagnosed by `diagnoseUnresolvedDotExprTypeRequirementFailure`.

Resolved: rdar://problem/45511837
When constructing requirement failures make sure that requirement
kind provided by the caller matches information about requirement
stored in the locator.
@xedin
Copy link
Contributor Author

xedin commented Oct 25, 2018

@swift-ci please smoke test

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