[FEAT] Detect constraint failure early in recursion circuit #1369
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
|
@noel2004 do you want to change the base branch to |
Ok |
Signed-off-by: noelwei <[email protected]>
noel2004
force-pushed
the
feat/recursion_fail_detective
branch
from
531d684 to
3fe82be
Compare
noel2004
changed the title
roynalnaruto
pushed a commit
that referenced
this pull request
Jul 18, 2024
Signed-off-by: noelwei <[email protected]>
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.
It is useness to run the proof of circuit if the equality constraints is not met in assigment step. So we detect them eariler.