[ConstraintSystem] Don't bind result type of an empty closure too early #30838
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of setting empty closure (
{}
) result type to beVoid
while generating constraints, let's allocate a new type variable
instead and let it be bound to
Void
once the body is opened.This way we can support an interaction with function builders which
would return a type different from
Void
even when applied to empty closure.Resolves: rdar://problem/61347993