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
+3
-3
@@ -14,7 +14,7 @@ fun Any?.isNull(): Boolean {
|
||||
|
||||
fun smartcastOnReceiver(x: Int?) {
|
||||
if (x.isNull()) {
|
||||
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
|
||||
x.<!UNSAFE_CALL!>inc<!>()
|
||||
}
|
||||
else {
|
||||
x.dec()
|
||||
@@ -26,10 +26,10 @@ class UnstableReceiver {
|
||||
|
||||
fun smartcastOnUnstableReceiver() {
|
||||
if (x.isNull()) {
|
||||
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
|
||||
x.<!UNSAFE_CALL!>inc<!>()
|
||||
}
|
||||
else {
|
||||
x.<!INAPPLICABLE_CANDIDATE!>dec<!>()
|
||||
x.<!UNSAFE_CALL!>dec<!>()
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user