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
+2
-2
@@ -23,7 +23,7 @@ fun bar(s: String?) {
|
||||
val hashCode = ss?.hashCode()
|
||||
ss = null
|
||||
if (hashCode != null) {
|
||||
ss.<!INAPPLICABLE_CANDIDATE!>hashCode<!>()
|
||||
ss.<!UNSAFE_CALL!>hashCode<!>()
|
||||
}
|
||||
}
|
||||
|
||||
@@ -41,6 +41,6 @@ fun baz(arg: Some?) {
|
||||
val ss = arg?.s
|
||||
if (ss != null) {
|
||||
arg.hashCode()
|
||||
arg.s.<!INAPPLICABLE_CANDIDATE!>hashCode<!>()
|
||||
arg.s.<!UNSAFE_CALL!>hashCode<!>()
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user