Dmitry Savvinov
d570b863ce
Introdude deprecation as per KT-21515. Warning is reported on type usage, that soon will became invisible. Quickfix by adding explicit import is added. Idea behind implementation is to mark scopes that are deprecated (see ClassResolutionScopesSupport). Then, during walk along hierarchy of scopes, look at deprecation status of the scope that has provided this classifier. Note that we also have to check if there are *some* non-deprecated visibility paths (because we can see classifier by two paths, e.g. if we've added explicit import) -- then this type reference shouldn't be treated as deprecated.
17 lines
342 B
Kotlin
Vendored
17 lines
342 B
Kotlin
Vendored
open class A {
|
|
class FromA {
|
|
fun foo() = 42
|
|
}
|
|
}
|
|
|
|
class B : A() {
|
|
companion object : A() { }
|
|
|
|
// we're seeing FromA here by two paths: one is deprecated (via companion object), and another one is not,
|
|
// so we shouldn't see deprecation warning
|
|
val a: FromA? = null
|
|
|
|
val b = FromA::foo
|
|
|
|
val c = FromA()
|
|
} |