I've got a collection of Duck objects and I'd like to sort them using multiple keys.
class Duck {
DuckAge age; //implements Comparable
DuckWeight weight; //implements Comparable
String name;
}
List<Duck> ducks = Pond.getDucks();
eg. I want to sort them primarily by their weights, and secondarily by their age. If two ducks have the exact same weight and the exact same age, then let's differentiate them using their names as a tertiary key. I might do something like this:
Collections.sort(ducks, new Comparator<Duck>(){
@Override
public int compare(Duck d1, Duck d2){
int weightCmp = d1.weight.compareTo(d2.weight);
if (weightCmp != 0) {
return weightCmp;
}
int ageCmp = d1.age.compareTo(d2.age);
if (ageCmp != 0) {
return ageCmp;
}
return d1.name.compareTo(d2.name);
}
});
Well I do this quite frequently, but this solution doesn't smell right. It doesn't scale well, and it's easy to mess up. Surely there must be a better way of sorting Ducks using multiple keys! Does anybody know of a better solution?
EDIT removed unnecessary else
branches
Java 8 solution:
Hooray for lambdas, method references, and default methods:)! Too bad we have to define getters, or use explicit lambdas, like so:
Type inference won't work with implicit lambdas, so you have to specify the argument type of the first two lambdas. More details in this answer by Brian Goetz.
You can use the CompareToBuilder from Apache Commons Lang. (It explains comparable, but works for Comparator too).
You can use chained
BeanComparators
from Commons BeanUtils:http://commons.apache.org/beanutils/v1.8.3/apidocs/org/apache/commons/beanutils/BeanComparator.html
I have just rewritten your code without nested else statements. Do you like it now?
Firstly, your solution isn't that slow.
If you really want another method, then give each duck a "score" which is essentially a single number that is the sum of their three characteristics, but with a huge weighting (excuse the almost unavoidable pun) for weight, a lesser one for age; and a very small one for the name.
You can allocate ~10 bits for each characteristic, so for each characteristic you have to be in the range
0..1023
.This is probably completely unneeded, but whatever :)