en passant: is IndexingObjectStore safe?
Cantor, Scott
cantor.2 at osu.edu
Wed Jan 15 11:44:48 EST 2014
On 1/15/14, 11:41 AM, "Ian Young" <ian at iay.org.uk> wrote:
>
>I should have said hashCode() explicitly, as that's what the class is
>using to detect "different" objects. My point is that this isn't
>sufficient to tell objects apart, unless you only define the class to be
>valid across objects where hashCode() comparison is the same as content
>equality, which is not in general the case.
It seems like actual equality here is the only foolproof test criteria for
reusing an object, though of course one would have to be certain the
objects stored implemented equals() correctly.
-- Scott
More information about the dev
mailing list