NI: exclude reporting of an unsafe call diagnostic for implicit invoke after safe call in cases when invoke has type parameters (make NI and OI consistent)
^KT-37579 Fixed
This commit is contained in:
+5
@@ -18790,6 +18790,11 @@ public class FirOldFrontendDiagnosticsTestGenerated extends AbstractFirOldFronte
|
||||
runTest("compiler/testData/diagnostics/tests/resolve/invoke/implicitInvoke.kt");
|
||||
}
|
||||
|
||||
@TestMetadata("implicitInvokeAfterSafeCall.kt")
|
||||
public void testImplicitInvokeAfterSafeCall() throws Exception {
|
||||
runTest("compiler/testData/diagnostics/tests/resolve/invoke/implicitInvokeAfterSafeCall.kt");
|
||||
}
|
||||
|
||||
@TestMetadata("invokeAndSmartCast.kt")
|
||||
public void testInvokeAndSmartCast() throws Exception {
|
||||
runTest("compiler/testData/diagnostics/tests/resolve/invoke/invokeAndSmartCast.kt");
|
||||
|
||||
Reference in New Issue
Block a user