feat: Implement byte@prove using range constraints
#182
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
This applies to all integer types, including `byte` and `nibble`. However, `binary` constraints are treated different and use vanishings constraints instead. There also remains an outstanding issue related to perspectives, in that the perspective selector is not being applied. This will be resolved separately in #101.
DavePearce
force-pushed
the
129-refactor-byteprove-to-use-range-constraints
branch
from
c6b8b76
to
efd60eb
Compare
DavePearce
changed the title
byte@prove using range constraintsbyte@prove using range constraints
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.
This applies to all integer types, including
byteandnibble. However,binaryconstraints are treated different and use vanishings constraints instead.There also remains an outstanding issue related to perspectives, in that the perspective selector is not being applied. This will be resolved separately in #101.