From c02923c5b5df9e38abc0e11a618952f75690eb34 Mon Sep 17 00:00:00 2001 From: Ilya Chernikov Date: Mon, 18 Jul 2022 17:07:20 +0200 Subject: [PATCH] [minor] FIR resolution for dynamics - use more appropriate prio --- .../kotlin/fir/resolve/calls/ResolutionDiagnostic.kt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/compiler/fir/semantics/src/org/jetbrains/kotlin/fir/resolve/calls/ResolutionDiagnostic.kt b/compiler/fir/semantics/src/org/jetbrains/kotlin/fir/resolve/calls/ResolutionDiagnostic.kt index bcd1192cec0..63808ab6cf4 100644 --- a/compiler/fir/semantics/src/org/jetbrains/kotlin/fir/resolve/calls/ResolutionDiagnostic.kt +++ b/compiler/fir/semantics/src/org/jetbrains/kotlin/fir/resolve/calls/ResolutionDiagnostic.kt @@ -97,9 +97,7 @@ class UnsafeCall(val actualType: ConeKotlinType) : ResolutionDiagnostic(UNSAFE_C object LowerPriorityToPreserveCompatibilityDiagnostic : ResolutionDiagnostic(RESOLVED_NEED_PRESERVE_COMPATIBILITY) -// TODO: change this to RESOLVED_LOW_PRIORITY after we are able to process dynamic extensions properly -// At the moment we stop resolve on synthetic dynamic members, which is not correct -object LowerPriorityForDynamic : ResolutionDiagnostic(K2_SYNTHETIC_RESOLVED) +object LowerPriorityForDynamic : ResolutionDiagnostic(RESOLVED_LOW_PRIORITY) object CandidateChosenUsingOverloadResolutionByLambdaAnnotation : ResolutionDiagnostic(RESOLVED)