Avoid calling unsupported computeHash in some situations #1632
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.
Some types do not implement
computeHash
, instead they overridemyHash
directly. This works fine as long asmyHash
is not equal toHashUnknown
but this was not guaranteed before this commit, ifmyHash
is equal toHashUnknown
thencomputeHash
is called byCachedGroundType#hash
orCachedProxyType#hash
causing an exception:https://gist.github.com/smarter/6b642db0495e995d8f3c26d614cf54d6
This commit fixes this by making sure we never compute a hash equal to
HashUnknown
, insteadHashUnknownAlt
should be used.Review by @odersky