[FIR] Don't report MUST_BE_INITIALIZED on private open properites
^KT-59074 Fixed This solution is not ideal. Ideally, the allopen compiler plugin shouldn't report `private` properites as `open` KT-64980, but it will unpredictably break other things.
This commit is contained in:
+6
@@ -3578,6 +3578,12 @@ public class DiagnosticCompilerTestFE10TestdataTestGenerated extends AbstractDia
|
||||
runTest("compiler/testData/diagnostics/tests/backingField/MustBeInitializedEffectivelyFinalOn.kt");
|
||||
}
|
||||
|
||||
@Test
|
||||
@TestMetadata("OpenPrivateValDeferredInit.kt")
|
||||
public void testOpenPrivateValDeferredInit() throws Exception {
|
||||
runTest("compiler/testData/diagnostics/tests/backingField/OpenPrivateValDeferredInit.kt");
|
||||
}
|
||||
|
||||
@Test
|
||||
@TestMetadata("OpenValDeferredInitError_InFinalClass_DisableEffectivelyFinal.kt")
|
||||
public void testOpenValDeferredInitError_InFinalClass_DisableEffectivelyFinal() throws Exception {
|
||||
|
||||
+6
@@ -3578,6 +3578,12 @@ public class LLFirPreresolvedReversedDiagnosticCompilerFE10TestDataTestGenerated
|
||||
runTest("compiler/testData/diagnostics/tests/backingField/MustBeInitializedEffectivelyFinalOn.kt");
|
||||
}
|
||||
|
||||
@Test
|
||||
@TestMetadata("OpenPrivateValDeferredInit.kt")
|
||||
public void testOpenPrivateValDeferredInit() throws Exception {
|
||||
runTest("compiler/testData/diagnostics/tests/backingField/OpenPrivateValDeferredInit.kt");
|
||||
}
|
||||
|
||||
@Test
|
||||
@TestMetadata("OpenValDeferredInitError_InFinalClass_DisableEffectivelyFinal.kt")
|
||||
public void testOpenValDeferredInitError_InFinalClass_DisableEffectivelyFinal() throws Exception {
|
||||
|
||||
Reference in New Issue
Block a user