FIR checker: differentiate UNSAFE_CALL from INAPPLICABLE_CANDIDATE
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.
This commit is contained in:
committed by
Mikhail Glukhikh
parent
4b823eca21
commit
e72ddbcbfe
@@ -27,7 +27,7 @@ fun case_2(x: Boolean?, y: Any?) {
|
||||
if (x == false) return
|
||||
if (y != x) {
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!INAPPLICABLE_CANDIDATE!>equals<!>(10)
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!UNSAFE_CALL!>equals<!>(10)
|
||||
}
|
||||
}
|
||||
|
||||
@@ -39,7 +39,7 @@ fun case_3(x : Unit?, y : Any?) {
|
||||
if (x == kotlin.Unit) return
|
||||
if (y != x) {
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!INAPPLICABLE_CANDIDATE!>equals<!>(10)
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!UNSAFE_CALL!>equals<!>(10)
|
||||
}
|
||||
}
|
||||
|
||||
@@ -51,7 +51,7 @@ fun case_4(x : EnumClassSingle?, y : Any?) {
|
||||
if (x == EnumClassSingle.EVERYTHING) return
|
||||
if (y != x) {
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!INAPPLICABLE_CANDIDATE!>equals<!>(10)
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>y<!>.<!UNSAFE_CALL!>equals<!>(10)
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user