This repository has been archived by the owner on Feb 24, 2021. It is now read-only.
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.
I made a few changes to the
Hash
typeclass to make it both easier to define and better to use.Eq
superclass from it. It never made sense and it should not have been there in the first place.hashWithSalt
. Allows for two nice things: First hashing with salt, but also allows very easy definitions for sum types:Either<L, R>.hash(HL: Hash<L>, HR: Hash<R>): Int = fold({ l -> HL.run { l.hashWithSalt(0) } }, { r -> HR.run { r.hashWithSalt(1) } })
Hashed
datatype. It carriers its precomputed hash and thus provides very fast inequality checks and provides itsHash
instances with the cached hash.Overall this makes
Hash
actually somewhat useful over the defaulthashCode
now :)