feat: support Sierra 1.5.0 new CASM hash algorithm #565
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xJonathanLEI
force-pushed
the
dev/sierra_1_5_0
branch
3 times, most recently
from
9ae415d to
a96c2da
Compare
Adds support for the new CASM hash algorithm introduced with Sierra 1.5.0. This implementation is very rough and inefficient, as it's meant to ship a working implementation as soon as possible, so that downstream tools (e.g. Starkli) can integrate sooner. Optimizations should be made later in follow-up PRs.
xJonathanLEI
force-pushed
the
dev/sierra_1_5_0
branch
from
a96c2da to
b8be178
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds support for the new CASM hash algorithm introduced with Sierra 1.5.0. This implementation is very rough and inefficient, as it's meant to ship a working implementation as soon as possible, so that downstream tools (e.g. Starkli) can integrate sooner. Optimizations should be made later in follow-up PRs.