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
@@ -9,5 +9,5 @@ fun <T> T?.let(f: (T) -> Unit) {
|
||||
fun test(your: Your?) {
|
||||
(your?.foo() as? Any)?.let {}
|
||||
// strange smart cast to 'Your' at this point
|
||||
your.<!INAPPLICABLE_CANDIDATE!>hashCode<!>()
|
||||
your.<!UNSAFE_CALL!>hashCode<!>()
|
||||
}
|
||||
Reference in New Issue
Block a user