[ https://issues.apache.org/jira/browse/COLLECTIONS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Neidhart resolved COLLECTIONS-552. ----------------------------------------- Resolution: Won't Fix The semantics of an EquatorMap would collide with the Map contract, thus closing as Won't fix for now. > Add an EquatorMap > ----------------- > > Key: COLLECTIONS-552 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-552 > Project: Commons Collections > Issue Type: New Feature > Affects Versions: 4.0 > Reporter: Thomas Neidhart > > An EquatorMap would use an Equator to compute the hashCode and make equality > checks for the keys. Sometimes there is the use case to put objects into a > map but their equals/hashCode implementation does not support that or one > needs a custom version. The usual solution is to put the object in some kind > of wrapper, but this requires additional memory. > By providing an Equator, one can create custom maps quite easily. The > implementation could be similar to the previous IdentityMap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)