Implement stack as enum and enhance stack value handling #4
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
Co-authored-by: Nuno Carvalho <[email protected]> Co-authored-by: abipalli <[email protected]>
…cking and cloning
Co-authored-by: João Conserva <[email protected]>
Co-authored-by: João Conserva <[email protected]>
…ility function for garbled uint to bool conversion
…terpreter modules
…for public and private values
…ehensive unit tests
… flow in contract deployment
…ging and private computation verification
…ns and usage examples
… feat/garbled-stack
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.
Introduce stack as an enum to improve type safety and simplify stack value handling. Fix various issues related to stack operations, including zero-checking and type conversions. Add a circuit builder and update related functionalities to ensure compatibility with the new stack implementation.