Please add a test that demonstrates the "why" of adding the hashCode() method.

According to the Java Language Specification, there is a contract between equals(Object) and hashCode():

If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. It is not required that if two objects are unequal according to the equals(java.lang.Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hashtables. 

In order to comply with this contract, those methods should be either both inherited, or both overridden.

Every functional update should be accompanied by one or more unit and integration tests.
Please add a test that demonstrates the "why" of adding the hashCode() method.

will add testHashCode()

On Tue, Feb 10, 2015 at 10:15 AM, Andrew Woods notifications@github.com
wrote:

Every functional update should be accompanied by one or more unit and
integration tests.
Please add a test that demonstrates the "why" of adding the hashCode()
method.

—
Reply to this email directly or view it on GitHub
#707 (comment).

Resolved with: c2e1af0