Skip to content

[Diagnostics] Don't re-typecheck function expression associated with various calls#29490

Merged
xedin merged 3 commits into
swiftlang:masterfrom
xedin:remove-more-code-from-visitapplyexpr
Jan 28, 2020
Merged

[Diagnostics] Don't re-typecheck function expression associated with various calls#29490
xedin merged 3 commits into
swiftlang:masterfrom
xedin:remove-more-code-from-visitapplyexpr

Conversation

@xedin
Copy link
Copy Markdown
Contributor

@xedin xedin commented Jan 28, 2020

Obsolete almost all of the logic related to re-typecheck of the function expression associated
with ApplyExpr.

xedin and others added 3 commits January 27, 2020 16:53
… be a hole

If type variable is allowed to be a hole and it can't be bound to
this particular (full resolved) type, just ignore this binding
instead of re-trying it later.
…ying arguments

If a type variable representing "function type" is a hole
or it could be bound to some concrete type with a help of
a fix, let's propagate holes to the "input" type. Doing so
provides more information to upcoming argument and result matching.
@xedin xedin requested a review from hborla January 28, 2020 01:21
@xedin
Copy link
Copy Markdown
Contributor Author

xedin commented Jan 28, 2020

@swift-ci please smoke test

Comment thread lib/Sema/CSDiag.cpp
return true;
}
}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@hborla I think once we implement "one fix in N solutions" ambiguity handling all of the logic below could be replaced with return false; :)

@xedin xedin merged commit c662a91 into swiftlang:master Jan 28, 2020
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