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,6 +9,6 @@ fun foo() {
|
||||
var y: My? = My(42)
|
||||
if (y!!.x != null) {
|
||||
y = My(null)
|
||||
(y + My(0)).x.<!INAPPLICABLE_CANDIDATE!>hashCode<!>()
|
||||
(y + My(0)).x.<!UNSAFE_CALL!>hashCode<!>()
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user