Shouldn't HashSet/Map use Arrays.hashCode(x[]) ?
Ulf Zibis
Ulf.Zibis at gmx.de
Fri Jun 4 15:49:44 UTC 2010
Otherwise e.g. int[] as key for HashSet/Map doesn't make any sense.
I use a class where the content of an int[] defines the uniqueness or
there instances.
Before I create a new instance, I have to check if there is just one for
the same int[] content.
Using the current HashSet/Map implementation does not serve this need.
It seems, that I should first instantiate a temporary object containing
the int[], hash it in the set/map, and later throw it away. :-(
Maybe another reason for solving
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6812862
-Ulf
More information about the core-libs-dev
mailing list