I need an example on how to use a comparable class on a HashSet
to get an ascending order. Let’s say I have a HashSet
like this one:
Use a TreeSet instead. It has a constructor taking a Comparator. It will automatically sort the Set
.
If you want to convert a HashSet
to a TreeSet
, then do so:
Set<YourObject> hashSet = getItSomehow();
Set<YourObject> treeSet = new TreeSet<YourObject>(new YourComparator());
treeSet.addAll(hashSet);
// Now it's sorted based on the logic as implemented in YourComparator.
If the items you have itself already implements Comparable and its default ordering order is already what you want, then you basically don't need to supply a Comparator
. You could then construct the TreeSet
directly based on the HashSet
. E.g.
Set<String> hashSet = getItSomehow();
Set<String> treeSet = new TreeSet<String>(hashSet);
// Now it's sorted based on the logic as implemented in String#compareTo().
HashSet "makes no guarantees as to the iteration order of the set." Use LinkedHashSet instead.
Addendum: I would second @BalusC's point about implementing Comparable and express a slight preference for LinkedHashSet, which offers "predictable iteration order ... without incurring the increased cost associated with TreeSet."
Addendum: @Stephen raises an important point, which favors @BalusC's suggestion of TreeMap
. LinkedHashSet
is a more efficient alternative only if the data is (nearly) static and already sorted.
HashSets do not guarantee iteration order:
This class implements the Set interface, backed by a hash table (actually a HashMap instance). It makes no guarantees as to the iteration order of the set; in particular, it does not guarantee that the order will remain constant over time. This class permits the null element.
You probably need to choose a different datastructure if you want to be able to control the iteration order (or indeed have one at all!)