FIR: fix mixed up expected and actual types in ArgumentTypeMismatch reporting
This commit is contained in:
committed by
TeamCityServer
parent
8d15e0e824
commit
d3913b85cf
+1
-1
@@ -64,8 +64,8 @@ fun Candidate.preprocessLambdaArgument(
|
|||||||
if (!csBuilder.addSubtypeConstraintIfCompatible(lambdaType, expectedType, position)) {
|
if (!csBuilder.addSubtypeConstraintIfCompatible(lambdaType, expectedType, position)) {
|
||||||
sink.reportDiagnostic(
|
sink.reportDiagnostic(
|
||||||
ArgumentTypeMismatch(
|
ArgumentTypeMismatch(
|
||||||
lambdaType,
|
|
||||||
expectedType,
|
expectedType,
|
||||||
|
lambdaType,
|
||||||
argument,
|
argument,
|
||||||
context.session.typeContext.isTypeMismatchDueToNullability(lambdaType, expectedType)
|
context.session.typeContext.isTypeMismatchDueToNullability(lambdaType, expectedType)
|
||||||
)
|
)
|
||||||
|
|||||||
Reference in New Issue
Block a user