No, no... good question.
I just think it would be wiser if users created a single, CompositeKey
class type, with properly implements equals and hashCode methods, as I
I don't see any advantage in using a java.util.Collection as a key over
implementing a CompositeKey type.
As such, anything we can do to discourage users from using Collection types
as a key, I think is a good thing.
On Thu, Nov 30, 2017 at 2:35 PM, Jason Huynh <[EMAIL PROTECTED]> wrote: