Mix in the productPrefix
hash statically in case class hashCode
#22865
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 2.13, case class
hashCode
mixes in the hash code of theproductPrefix
string. This is inconsistent with theequals
method, subclasses of case classes that overrideproductPrefix
compare equal but have a differenthashCode
(scala/bug#13033).This commit changes
hashCode
to mix in theproductPrefix.hashCode
statically instead of invokingproductPrefix
at runtime.For case classes without primitive fields, the synthetic
hashCode
invokesScalaRunTime._hashCode
, which mixes in the result ofproductPrefix
. To fix that, the synthetic hashCode is changed to invokeMurmurHash3.productHash
directly and mix in the name to the seed statically.Scala 3 forward port of scala/scala#11023