[FIR] 2/2 Support more wider actual member visibility, if the expect member is effectively final
^KT-61955 Fixed Introduce LV vs don't introduce LV: introduce LV: - K1 IDE and K2 project: IDE accurately shows compiler errors - K2 IDE and K1 project: There are cases when IDE shows red but in reality it's green don't introduce LV: - K1 IDE and K2 project: There are cases when IDE shows red but in reality it's green - K2 IDE and K1 project: There are cases when IDE shows green but in reality it's red
This commit is contained in:
@@ -303,6 +303,7 @@ enum class LanguageFeature(
|
||||
KeepNullabilityWhenApproximatingLocalType(KOTLIN_2_0, kind = BUG_FIX), // KT-53982
|
||||
ProhibitAccessToInvisibleSetterFromDerivedClass(KOTLIN_2_0, kind = BUG_FIX), // KT-56662
|
||||
ProhibitOpenValDeferredInitialization(KOTLIN_2_0, kind = BUG_FIX), // KT-57553
|
||||
SupportEffectivelyFinalInExpectActualVisibilityCheck(KOTLIN_2_0, kind = BUG_FIX), // KT-61955
|
||||
ProhibitMissedMustBeInitializedWhenThereIsNoPrimaryConstructor(KOTLIN_2_0, kind = BUG_FIX), // KT-58472
|
||||
MangleCallsToJavaMethodsWithValueClasses(KOTLIN_2_0, kind = OTHER), // KT-55945
|
||||
ForbidInferringTypeVariablesIntoEmptyIntersection(KOTLIN_2_0, kind = BUG_FIX), // KT-51221
|
||||
|
||||
Reference in New Issue
Block a user