FIR: Rewrite visibility checking
Unbound it from implicit receiver stack as it only needs scope structure/declaration nestedness Semantics for protected has been changed in a way it works in old FE NB: We should report additional diagnostic in case of CallCompanionProtectedNonStatic.fir.kt (see KT-38814)
This commit is contained in:
+3
-3
@@ -48,7 +48,7 @@ class Derived : Base() {
|
||||
foo() // Ok
|
||||
gav() // Ok
|
||||
bar()
|
||||
<!INAPPLICABLE_CANDIDATE!>baz<!>()
|
||||
baz()
|
||||
prop = 0
|
||||
}
|
||||
|
||||
@@ -57,7 +57,7 @@ class Derived : Base() {
|
||||
foo() // Ok
|
||||
gav() // Ok
|
||||
bar()
|
||||
<!INAPPLICABLE_CANDIDATE!>baz<!>()
|
||||
baz()
|
||||
prop = 0
|
||||
}
|
||||
}
|
||||
@@ -66,7 +66,7 @@ class Derived : Base() {
|
||||
fun test2() {
|
||||
gav() // Ok
|
||||
bar()
|
||||
<!INAPPLICABLE_CANDIDATE!>baz<!>()
|
||||
baz()
|
||||
prop = 0
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user