Benefit from computing String Hash at compile time?
alexander.veit at gmx.net
Mon Jan 4 15:01:34 PST 2010
> The fact is, the spec is set in stone, *and* covered by conformance
> tests. The chance of the spec changing is vanishingly small, and the
> conformance tests ensure that all implementations of Java must follow
> the spec.
Calculating String#hashCode() is quite costly in terms of CPU cycles. If a
better performing method with comparable quality would come to our
knowledge, the chance of changing the spec would probably be greater than e
More information about the coin-dev