Description Martin Fabricius 2019-07-09 05:19:49 EDT

Syntax coloring of Auto(un)boxed values has some issues with the ternary operator. Consider the following cases: (t() is just a boolean function to get the compiler to not ignore the else case)

void autoBoxing() {
    Long l = t() ? 20L : 0L; // working as inteded, both marked
}
-------------------------
void autoBoxing() {
    long l = t() ? getLong() : 0L; // working as inteded, getLong() is marked
}
private Long getLong() {
    return Long.valueOf(0L);
}
-------------------------
void autoBoxing() {
    long l = t() ? getLong() : getLong(); // NOT working, nothing marked
}
private Long getLong() {
    return Long.valueOf(0L);
}
-------------------------
void autoBoxing() {
    Long l = t() ? getLong() : 0L; // NOT working, only 0L marked
}
private long getLong() {
    return 0L;
}
-------------------------
void autoBoxing() {
    Long l = t() ? getLong() : getLong(); // NOT working, nothing marked
}
private long getLong() {
    return 0L;
}

The problem with all these cases is that "INVOKEVIRTUAL Long.longValue() : long" does not come immediately after the long getter/loader but in another bytecode branch after a "GOTO" with a "FRAME SAME1 long" in between.