mirror of
https://github.com/apple/swift.git
synced 2026-10-26 20:15:53 +01:00
Hamish Knight
0993a79da7
We can fix a call of a non-function type by recording `RemoveInvalidCall`, but may still record other fixes that want to check whether a locator has function arg apply info associated with it. Given the base expression can basically be any expression node in this case, trying to assert whether or not we expect a callee locator to be set is pretty fragile and isn't really providing any real value, especially as it's a lowercase `assert`. Let's just drop it. We'll bail from `getFunctionArgApplyInfo` if we don't have an actual function type.
6 lines
563 B
Swift
6 lines
563 B
Swift
// {"kind":"complete","original":"22c5dffd","signature":"swift::constraints::Solution::getFunctionArgApplyInfo(swift::constraints::ConstraintLocator*) const","signatureAssert":"Assertion failed: (!shouldHaveDirectCalleeOverload(call) && \"Should we have resolved a callee for this?\"), function getFunctionArgApplyInfo","signatureNext":"ArgumentTypeCheckCompletionCallback::sawSolutionImpl"}
|
|
// RUN: %target-swift-ide-test -code-completion -batch-code-completion -skip-filecheck -code-completion-diagnostics -source-filename %s
|
|
struct a {
|
|
ap { a<b>(c( #^^#
|
|
}
|