Skip to content

[TypeChecker] Disable expression diagnostics for code completion #17980

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
Jul 16, 2018

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jul 16, 2018

Any produced diagnostics are suppressed anyway by a special
diagnostic engine attached to the new type-checker, so there
no point of doing any of that work.

Resolves: rdar://problem/22996887

xedin added 2 commits July 15, 2018 23:23
…es flags

Instead of mixing flags between type-checker and constraint solver, let's
move the ones which are useful in constraint system there. Doing
so allows for `solveForExpression` to be moved from `TypeChecker` to
`ConstraintSystem` which consolidates solver logic.

It also allows to set these flags as part of constraint generation/solving,
which is sometimes important.
Any produced diagnostics are suppressed anyway by a special
diagnostic engine attached to the new type-checker, so there
no point of doing any of that work.

Resolves: rdar://problem/22996887
@xedin xedin requested a review from rudkx July 16, 2018 19:19
@xedin
Copy link
Contributor Author

xedin commented Jul 16, 2018

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Jul 16, 2018

@swift-ci please test source compatibility

@xedin
Copy link
Contributor Author

xedin commented Jul 16, 2018

/cc @nathawes as FYI

@xedin xedin merged commit c997080 into swiftlang:master Jul 16, 2018
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