From: Maaartin G <grajc...@seznam.cz>
Date: Mon, 2 Jul 2012 07:17:07 -0700 (PDT)
Local: Mon, Jul 2 2012 10:17 am
Subject: Re: [guava] Is it worth commenting that Strings.common* expose potential memory leak from JDK String?
On Monday, July 2, 2012 12:10:54 PM UTC+2, Éamonn McManus wrote:In the first place it should never have been specified. But I would not
> If I recall correctly, the String.hashCode() algorithm used to be
call the algorithm awful, although I see no reason for it working the way
- Multiplication by 31 can't be optimized especially well using
Switching to any other deterministic algorithm does NOT help at all. Even
The determinism is the main problem here, the particular algorithm doesn't
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.