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
+2
-2
@@ -17,7 +17,7 @@ fun CharSequence?.isNullOrEmpty(): Boolean {
|
||||
fun smartcastOnReceiver(s: String?) {
|
||||
with(s) {
|
||||
if (isNullOrEmpty()) {
|
||||
<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
<!UNSAFE_CALL!>length<!>
|
||||
}
|
||||
else {
|
||||
length
|
||||
@@ -32,7 +32,7 @@ fun mixedReceiver(s: String?) {
|
||||
}
|
||||
} else {
|
||||
with(s) {
|
||||
<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
<!UNSAFE_CALL!>length<!>
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user