[FIR] Fix candidate success check by checking if no diagnostic is unsuccessful

Checking the current applicability isn't enough because in the presence
of multiple diagnostics, the lowest applicability can be successful but
a higher one isn't.

#KT-63147 Fixed
This commit is contained in:
Kirill Rakhman
2023-11-03 12:06:01 +01:00
committed by Space Team
parent 0d36462c58
commit 6b7eeec181
8 changed files with 75 additions and 10 deletions
@@ -28455,6 +28455,12 @@ public class DiagnosticCompilerTestFE10TestdataTestGenerated extends AbstractDia
runTest("compiler/testData/diagnostics/tests/resolve/dslMarker/kt46969.kt");
}
@Test
@TestMetadata("lowPriority.kt")
public void testLowPriority() throws Exception {
runTest("compiler/testData/diagnostics/tests/resolve/dslMarker/lowPriority.kt");
}
@Test
@TestMetadata("markedReceiverWithCapturedTypeArgument.kt")
public void testMarkedReceiverWithCapturedTypeArgument() throws Exception {
@@ -28455,6 +28455,12 @@ public class LLFirPreresolvedReversedDiagnosticCompilerFE10TestDataTestGenerated
runTest("compiler/testData/diagnostics/tests/resolve/dslMarker/kt46969.kt");
}
@Test
@TestMetadata("lowPriority.kt")
public void testLowPriority() throws Exception {
runTest("compiler/testData/diagnostics/tests/resolve/dslMarker/lowPriority.kt");
}
@Test
@TestMetadata("markedReceiverWithCapturedTypeArgument.kt")
public void testMarkedReceiverWithCapturedTypeArgument() throws Exception {