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:
Jinseong Jeon
2021-01-26 16:03:27 -08:00
committed by Mikhail Glukhikh
parent 4b823eca21
commit e72ddbcbfe
275 changed files with 1426 additions and 1388 deletions
@@ -20,28 +20,28 @@ fun myEqualsNotNull(x: Int?): Boolean {
}
fun testBasicEquals(x: Int?) {
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
if (myEqualsNull(x)) {
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
}
else {
x.inc()
}
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
}
fun testBasicNotEquals(x: Int?) {
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
if (myEqualsNotNull(x)) {
x.inc()
}
else {
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
}
x.<!INAPPLICABLE_CANDIDATE!>inc<!>()
x.<!UNSAFE_CALL!>inc<!>()
}