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
+1
-1
@@ -15,7 +15,7 @@ class A() {
|
||||
|
||||
fun case1() {
|
||||
var b: Case1? = Case1()
|
||||
<!INAPPLICABLE_CANDIDATE!>--<!>b?.a
|
||||
<!UNSAFE_CALL!>--<!>b?.a
|
||||
}
|
||||
|
||||
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ class A() {
|
||||
|
||||
fun case1() {
|
||||
var b: Case1? = Case1()
|
||||
<!INAPPLICABLE_CANDIDATE!>++<!>b?.a
|
||||
<!UNSAFE_CALL!>++<!>b?.a
|
||||
}
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user