Skip to content

[ConstraintSystem] Record produced types incrementally #37981

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
Jun 22, 2021

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jun 17, 2021

Allow type variable binding producer to record types as they
are being produced. Otherwise it could be possible to re-discover
already explored types during computeNext() which leads to
duplicate bindings e.g. inferring fallback Void for a closure
result type when Void was already inferred as a direct/transitive
binding.

xedin added 2 commits June 17, 2021 13:47
Allow type variable binding producer to record types as they
are being produced. Otherwise it could be possible to re-discover
already explored types during `computeNext()` which leads to
duplicate bindings e.g. inferring fallback `Void` for a closure
result type when `Void` was already inferred as a direct/transitive
binding.
Make sure that `Void` doesn't get attempted twice if it was
inferred directly or transitively.
@xedin xedin requested a review from hborla June 17, 2021 21:13
@xedin
Copy link
Contributor Author

xedin commented Jun 22, 2021

@swift-ci please smoke test

@xedin xedin merged commit 21084b4 into swiftlang:main Jun 22, 2021
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