e72ddbcbfe
To do so, inside the root cause of inapplicable candidate errors, we will record expected/actual type of receiver, if any. That will help identifying inapplicable calls on nullable receiver.
23 lines
561 B
Kotlin
Vendored
23 lines
561 B
Kotlin
Vendored
// !WITH_NEW_INFERENCE
|
|
class Data<T>(val x: T, val y: T)
|
|
|
|
operator fun <T> Data<T>.component1() = x
|
|
|
|
operator fun <T> Data<T>.component2() = y
|
|
|
|
fun foo(): Int {
|
|
val d: Data<Int>? = null
|
|
// An error must be here
|
|
val (x, y) = <!COMPONENT_FUNCTION_ON_NULLABLE, COMPONENT_FUNCTION_ON_NULLABLE!>d<!>
|
|
return x + y
|
|
}
|
|
|
|
data class NormalData<T>(val x: T, val y: T)
|
|
|
|
fun bar(): Int {
|
|
val d: NormalData<Int>? = null
|
|
// An error must be here
|
|
val (x, y) = <!COMPONENT_FUNCTION_ON_NULLABLE, COMPONENT_FUNCTION_ON_NULLABLE!>d<!>
|
|
return x + y
|
|
}
|