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
Vendored
+1
-1
@@ -9,5 +9,5 @@ fun checkJump(x: Int?, y: Int?) {
|
||||
y.hashCode()
|
||||
}
|
||||
// Smart cast here is erroneous: y is nullable
|
||||
y.<!INAPPLICABLE_CANDIDATE!>hashCode<!>()
|
||||
y.<!UNSAFE_CALL!>hashCode<!>()
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user