HashMap vs HashSet is the most frequently asked question during any core java interview and interview is not said completed until they will not cover the Collection Framework and multi-threading interview and collections are uncompleted without Covering Hash Set and Hash Map.
HashSet is implementation of Set Interface which does not allow duplicate value all the methods which are in Collection Framework are also in Set Interface by default but when we are talking about Hash set the main thing is objects which are going to be stored in HashSet must override equals() and hashCode() method so that we can check for equality and no duplicate value are stored in our set.if we have created our own objects we need to implement hashCode() and equal() in such a manner that will be able to compare objects correctly when storing in a set so that duplicate objects are not stored,if we have not override this method objects will take default implementation of this method.
You can read more about HashMap in my article How HashMap works in Java and Difference between HashMap and hashtable in Java
Difference between HashSet and HashMap in Java
HashMap is a implementation of Map interface | HashSet is an implementation of Set Interface |
HashMap Stores data in form of key value pair | HashSet Store only objects |
Put method is used to add element in map | Add method is used to add element is Set |
In hash map hashcode value is calculated using key object | Here member object is used for calculating hashcode value which can be same for two objects so equal () method is used to check for equality if it returns false that means two objects are different. |
HashMap is faster than hashset because unique key is used to access object | HashSet is slower than Hashmap |
10 examples of SimpleDateFormat in Java
How to resolve OutOfMemoryError in Java
How to deal with UnSupportedClassVersionError in Java
Key differences between Vector and ArrayList in java
Difference between StringBuffer and StringBuilder in Java
ArrayList tutorial with examples on Java 1.5 generics
No comments:
Post a Comment