Hello, > Just being Devil's advocate for a moment but.... > Couldn't this kind of thing be done with custom Comparators and (say) > TreeMap?
Of course it could. But everyone knows that HashMap is much more efficient than TreeMap, and so is the wrapper I described. This allows not to be constrained to particular Map implementation. Another thing is that I do not understand the real use case laying behind the discussed Transform-xxx. I do not see why somebody wants to put transformed elements into a collection, but ask for them directly. It breaks some natural laws, like: map.put(x, y); map.containsKey(x); // this should be true I think that this may be very misleading for many people, and be the reason of hard-to-find errors. IMHO this idea breaks basic Collection Framework intuitions. However, this Predicate-xxx stuff is a completely different story and a good idea I think. Regards, Michal -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
