Could we merge some or all of ComparableQuantity into Quantity?

[keilw]

Unlike key elements of JSR 354 (CurrencyUnit or MonetaryAmount) Quantity (as well as Unit) neither apply Comparable nor other interfaces like Serializable.
On an implementation level ComparableQuantity was introduced for that reason. While Serializable is questionable outside the implementation (also see #43 or how JSR 354 keeps it in the RI) Comparable and maybe at least some methods in ComparableQuantity could be beneficial to Quantity.

[otaviojava]

The issue in the sort is what happens when we have different unit types in the list?
E.g.: day, hour, byte, km/h

IMHO: that should be outside of the API

[keilw]

Hard to say, the list could still be strongly typed with Quantity<Time> or Quantity<Speed> in such case. Implementing would still be in the RI but let's see what others think.

[otaviojava]

If you create our list yes, however, java is Type Erasure. So we don't have any control about that.

[keilw]

Of course even JavaMoney has a hard time to compare multiple amounts in a list, if the CurrencyUnit is not the same. It could be done, but makes no sense without explicit conversion (which unlike UoM requires access to live exchange rates)

[keilw]

In the Hangout we found too little synergies or strong arguments for API inclusion, therefore leaving the interface in the RI for now.