Skip to content

[ConstraintSystem] Always verify computed/resolved pattern types befo… #31604

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
May 7, 2020

Conversation

xedin
Copy link
Contributor

@xedin xedin commented May 6, 2020

…re use

While trying to infer type for pattern always take result of
getTypeForPattern and resolveTypeInExpressionContext with
a grain of salt because both of these methods produce empty type
if type as-written or one of the sub-pattern types is incorrect.

Resolves: rdar://problem/60534522

@xedin xedin requested a review from DougGregor May 6, 2020 22:46
@xedin
Copy link
Contributor Author

xedin commented May 6, 2020

@swift-ci please smoke test

…re use

While trying to infer type for pattern always take result of
`getTypeForPattern` and `resolveTypeInExpressionContext` with
a grain of salt because both of these methods produce empty type
if type as-written or one of the sub-pattern types is incorrect.

Resolves: rdar://problem/60534522
@xedin xedin force-pushed the rdar-60534522 branch from a53f8da to f22ca72 Compare May 6, 2020 22:58
@xedin
Copy link
Contributor Author

xedin commented May 6, 2020

@swift-ci please smoke test

@xedin
Copy link
Contributor Author

xedin commented May 6, 2020

@swift-ci please smoke test macOS platform

@xedin
Copy link
Contributor Author

xedin commented May 6, 2020

@swift-ci please smoke 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.

2 participants