Why Override Equals, Hashcode As Well As Tostring Method Inwards Java

Couple of questions, which are ofttimes asked to me was why exercise nosotros demand to override equals() in addition to hashcode() method, Why should I implement toString(), What volition plow over off if I don't override them or inwards a dissimilar way, I direct maintain never overridden equals in addition to hashcode in addition to non faced whatsoever problem, why should I override them now. You guessed it correct, nigh all of these questions comes from beginners, who direct maintain either taken some Java programming classes, or started learning Java yesteryear their own. Though concept of equality is something yous cannot ignore, right agreement of equals(), hashcode(), toString() in addition to another method from java.lang.Object class, ofttimes goes unnoticed, at to the lowest degree until they self-realize it or Interviewer forcefulness them to explore that part. I direct maintain already written twosome of articles on equals in addition to hashcode, e.g. equals vs ==,  hashcode tips, equals in addition to hashcode interview questions and 1 of my personal favorite, five tips to override equals inwards Java, which already touches this acre of written report but I idea to explicate it clearly hither for in 1 trial in addition to all.

Why yous should override equals or hashcode

From the face, yous tin guess that equals() is used to depository fiscal establishment jibe if ii objects are equal or not. Now this equality tin last defined inwards ii ways, identity equality in addition to logical equality, equally I explained inwards equals vs == post, it's the logical equality, which is taken attention yesteryear equals method.

If yous are doing Java programming than yous in all probability know that every course of education inwards Java implicitly inherit from java.lang.Object, in addition to from at that spot every object inherit equals() in addition to hashcode(). There default implementation is inwards business amongst == operator, i.e. equals() supply identity equality in addition to render truthful if reference variable pointing to same object. Now, if yous don't demand logical equality, thus yous don't demand to override equals, but the employment is yous volition demand it. All your domain object e.g. Order, Trade, Message tin last compared to each other in addition to yous demand logical comparison. One of the pop instance is java.lang.String class, which needs logical comparing i.e. grapheme based comparison. If ii String object contains same characters inwards same guild they are considered equals, which is what yous demand inwards many programming task. Similarly, all domain object has equality defined, but truthful demand of equals in addition to hashcode arise, when yous role them equally key inwards hash based collection e.g. Hashtable or HashMap. These collection classes relies on rules of  Java programming approximately equals in addition to hashcode to run according to their specification, popularly known equally equals-hashcode contract. According to which, you must override hashcode, if yous are overriding equals and vice-versa. Problem is that this is non enforced yesteryear compiler, in addition to if yous brand such mistake, your plan volition non run properly.

For example, whatsoever object which doesn't follows equals in addition to hashcode contract, if used equally key inwards HashMap, yous may non last able to retrieve object again, encounter how HashMap plant internally inwards Java for to a greater extent than details. In short, yous demand to override equals in addition to hashcode, if yous are writing a domain object, or yous desire to shop them inwards hash based collection. Once yous empathize why yous should override equals in addition to hashcode, in addition to when yous should exercise that, it's slow to genuinely exercise that. See my postal service five tips to override equals in addition to hashcode inwards Java for to a greater extent than details.

Why yous demand to override toString method

You should override toString() method for all domain object, because whenever yous impress them using logger or System.out.println() statements, at that spot toString() method is called. Since default implementation of toString() is non real helpful, in addition to entirely impress classname@hashcode e.g. com.test.User@1033203. If yous impress some useful information, e.g. Arun, 1022320,  it volition entirely assist yous during debugging in addition to troubleshooting. Now at that spot are multiple ways to override toString() inwards Java, encounter that link for some slow in addition to productive way. For  example, if yous impress array inwards Java yous volition non encounter whatsoever meaningful value, because it doesn't override toString() method, but yous tin withal print arrays yesteryear using Arrays.toString() method. This volition straightaway exhibit yous elements stored inwards array, instead of but type of array in addition to it's hashcode.

I promise this assist yous to empathize significance of equals, hashcode in addition to toString method inwards Java. In fact all methods of java.lang.Object are worth reading. These are key concept in addition to company noesis of this volition entirely going to assist you, both during Interview in addition to on Job. Time spent on agreement java.lang, java.util in addition to java.io are best investment inwards learning Java. Always think to override hashcode() if yous are overriding equals() method in addition to vice-versa. Failing to exercise thus is non a compile fourth dimension error but tin exercise genuinely subtle bugs which tin direct maintain hours to debug in addition to solve, for instance your HashMap reduced to linked listing due to frequent collision, yous non able to retrieve object set on HashMap etc.

Further Reading
Complete Java Masterclass
Java Fundamentals: The Java Language
Java In-Depth: Become a Complete Java Engineer!
Java Programming Interview Exposed
Cracking the code interview - 189 qustions in addition to solutions

Share this post