.equals(x) is probably not intended

this intention produces false positives now (4069)
should only warn if parameter is null, but seems to do on every .equals

4 comments

Bas, i see also this:
if (o != null) {
obj.equals(o); // Here is Object.equals(null) marked
}

0

Yep, same problem. Everywhere object.equals(something) is marked and object.equals(null) isn't. I recommend to disable this inspection until the next build.

Bas

0

Please sign in to leave a comment.