Currently trove collections rely on usual == comparison of types. This might be a problem for floating point types because of precision problem. For example, TDoubleSet.contains(double v) method is not very useful because in current implementations it will be compare for exact equality and will return false most of the time(no place where I can provide my epsilon). Same issue with sorting. So, I thought it might be good to introduce custom comparator into implementations of floating type collections.
Issue #39 duplicate