Do not check argumentMapping.isError()
Argument matching status can be considered an "error" in resolve, even though it is not a compilation error and doesn't prevent code from being generated. Actually, we should only check if the argument matching status is ArgumentMatch. #KT-18294 Fixed
This commit is contained in:
@@ -467,6 +467,12 @@ public class IrTextTestCaseGenerated extends AbstractIrTextTestCase {
|
||||
KotlinTestUtils.assertAllTestsPresentByMetadata(this.getClass(), new File("compiler/testData/ir/irText/expressions"), Pattern.compile("^(.+)\\.kt$"), TargetBackend.ANY, true);
|
||||
}
|
||||
|
||||
@TestMetadata("argumentMappedWithError.kt")
|
||||
public void testArgumentMappedWithError() throws Exception {
|
||||
String fileName = KotlinTestUtils.navigationMetadata("compiler/testData/ir/irText/expressions/argumentMappedWithError.kt");
|
||||
doTest(fileName);
|
||||
}
|
||||
|
||||
@TestMetadata("arrayAccess.kt")
|
||||
public void testArrayAccess() throws Exception {
|
||||
String fileName = KotlinTestUtils.navigationMetadata("compiler/testData/ir/irText/expressions/arrayAccess.kt");
|
||||
|
||||
Reference in New Issue
Block a user