There's a Trove feature I didn't address in the 0.3 version of collections: control of the hash function for Object types. In Trove, you construct over a 'strategy' object if you want something like the JDK IdentityHashMap. COLT didn't do that. A user can get this currently via subclassing, though they have to subclass the primitive side of the house one-class-at-a-time. Some choices include:
1) Include Identity flavors ourself. 2) Adopt the strategy pattern, which is an extensibility pattern that allows users to implement one object and use it with all of the Object hashed containers. 3) something else I haven't thought of?
