what is the design decision behind LinkedHashSet implementation.

Asked Jun 18 '15 at 14:48

Active Jun 18 '15 at 14:48

Viewed 32 times

A quick look at javadoc:

public class LinkedHashSet<E>     
   extends HashSet<E>     
     implements Set<E>, Cloneable, Serializable

Why did they implement Set when it has already been implemented in HashSet? I had a look at this but I don't believe this was just a mistake.

edited May 23 '17 at 12:05

Community

asked Jun 18 '15 at 14:48

Akki

Josh was directly asked about that and he said that it was a mistake. – Davide Lorenzo MARINO Jun 18 '15 at 14:53
As I said, those answers are not convincing. – Akki Jun 18 '15 at 14:53
Also Einstein did mistakes in his life... why Josh can't? – Davide Lorenzo MARINO Jun 18 '15 at 14:55
Did "they" really implement it over again? If it is just in the class header it doesn't mean the methods have been implemented in LinkedHashSet - they have been inherited. – laune Jun 18 '15 at 14:56
then what was the need of "implements Set" ? – Akki Jun 18 '15 at 15:00
I did this occasionally to tell the reader of the Javadoc what is implemented *without having to go through some parent classes*. Don't know why "they" did it, but it's a good reason. - Note that HashSet and AbstractSet also have `implements Set`. – laune Jun 18 '15 at 15:08

0 Answers0