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
@@ -142,7 +142,7 @@ fun case_11() {
|
||||
x as? Any ?: null!!
|
||||
do {
|
||||
<!DEBUG_INFO_EXPRESSION_TYPE("kotlin.Any?")!>x<!>
|
||||
x = x.<!INAPPLICABLE_CANDIDATE!>equals<!>(10)
|
||||
x = x.<!UNSAFE_CALL!>equals<!>(10)
|
||||
} while (x != null)
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user