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
@@ -3,21 +3,21 @@ fun foo(x: String?, y: String?, z: String?, w: String?) {
if (x != null && y != null && (x == z || y == z))
z.length
else
z.<!INAPPLICABLE_CANDIDATE!>length<!>
z.<!UNSAFE_CALL!>length<!>
if (x != null || y != null || (x != z && y != z))
z.<!INAPPLICABLE_CANDIDATE!>length<!>
z.<!UNSAFE_CALL!>length<!>
else
z.<!INAPPLICABLE_CANDIDATE!>length<!>
z.<!UNSAFE_CALL!>length<!>
if (x == null || y == null || (x != z && y != z))
z.<!INAPPLICABLE_CANDIDATE!>length<!>
z.<!UNSAFE_CALL!>length<!>
else
z.length
if (x != null && y == x && z == y && w == z)
w.length
else
w.<!INAPPLICABLE_CANDIDATE!>length<!>
w.<!UNSAFE_CALL!>length<!>
if ((x != null && y == x) || (z != null && y == z))
y.length
else
y.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!UNSAFE_CALL!>length<!>
}