Todd O'Bryan (toddobryan) said:
This also occurs when you use a Java library that defines an eq method. Since you have no control over whether the library decided to use that name, and there was no reason in Java for the developers not to have used that name, it seems like it should be possible to suppress the warning.
Jed Wesley-Smith (jedws) said:
We see the problem as outlined by Todd. It is library that we do not control and therefore Rex's suggestion doesn't apply. The warning is particularly misleading as the return type of the eq method in question is not Boolean.