This week's book giveaway is in the Testing forum. We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line! See this thread for details.
If the default hashCode() produces distinct values for each object created why do we need to override it when using Maps ? If two objects having same instances are created naturally equals() ( which is overriden ) will return false and will not get stored in a map. So is not efficient enough to just override equals() for high performance ( fast access ) because each object is in a distinct 'bucket' and searching and comparing with just one object in the 'bucket' is required ?
The contract for equals() and hashCode() is that when equals() returns true when comparing two objects, then hashCode() must return the same value for those two objects. So objects that are equal must have the same hash code (see the API documentation of the hashCode() method in class Object, which explains this).
If you have overridden equals(), then you must also override hashCode() to make sure that this contract isn't broken. How you must implement hashCode() in such a case depends on how you implemented the equals() method.
It's not just for performance reasons that you need to override hashCode() if you've overridden equals() - it's because you must make sure that the contract as described above isn't broken.
If your class does break the contract, then unpredictable things might occur if you store instances of your class in a collection that uses hash codes (such as HashSet or HashMap). [ September 10, 2007: Message edited by: Jesper Young ]