FIR: fix mixed up expected and actual types in ArgumentTypeMismatch reporting

This commit is contained in:
Ilya Kirillov
2021-09-28 18:11:53 +02:00
committed by TeamCityServer
parent 8d15e0e824
commit d3913b85cf
@@ -64,8 +64,8 @@ fun Candidate.preprocessLambdaArgument(
if (!csBuilder.addSubtypeConstraintIfCompatible(lambdaType, expectedType, position)) {
sink.reportDiagnostic(
ArgumentTypeMismatch(
lambdaType,
expectedType,
lambdaType,
argument,
context.session.typeContext.isTypeMismatchDueToNullability(lambdaType, expectedType)
)