refactor: Add Anoma Node in Tree language #2784
Merged
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
Similarly to how the Cairo operations are handled we add a separate Tree language Node for Anoma operations instead of handling then as an Unop Node.
paulcadman
force-pushed
the
refactor-anoma-tree-node
branch
from
66420f2 to
9b17f9c
Compare
janmasrovira
approved these changes
May 17, 2024
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.
Similarly to how the Cairo operations are handled we add a separate Tree language Node for Anoma operations instead of handling them as an Unop Node.
This is necessary because we need to add support for new Anoma operations that are not unary.
This PR also adds support for
anoma-encodeandanoma-decodefunctions injvttree source files which was missed in the previous PRs.