Consider the following code:

public class A {

    public static void main(String... args) throws Exception {

        final Object o = getObject();

        if (o == null) {

        }

        if (true && o == null) {

        } else {
            System.out.println(
                    o.toString()
            );
        }
    }

    public static Object getObject() {
        return new Object();
    }
}


On the line where the object's toString() method is called, the hint "Dereferencing possible null pointer" is given.

Considering the "if-else-if" construction, o could never be null on the line where the hint is given.

However, removing the first "if" statement with the expression "o == null", somehow removes the hint as well.

It seems like a preceding if statement can unjustly affect the editor's state on determining whether the object could be null, as if the situation is too complex to be able to correctly determine this.