Files
swift-mirror/validation-test/compiler_crashers_fixed/Solution-getFunctionArgApplyInfo-166f11.swift
Hamish Knight 0993a79da7 [CS] Remove shouldHaveDirectCalleeOverload
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.
2026-05-21 12:28:22 +01:00

6 lines
530 B
Swift

// {"kind":"typecheck","original":"e34f553a","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":"MissingOptionalUnwrapFailure::offerDefaultValueUnwrapFixIt"}
// RUN: not %target-swift-frontend -typecheck %s
func a<each b>(c: repeat each b?, d: repeat (each b) -> Bool) {
repeat (d(c))
}