Refactor conditional statements #55
Merged
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.
Overview
Currently conditional statements create branches in code where only one path is enforced in the underlying circuit.
Changes
First, we need a gadget that can conditionally enforce assertion statements #52. This will ensure that all branch paths of a conditional statement are enforced.
With our new gadget we can now write assert statements inside the branch of a conditional.
Consider the function
enforceBit()
which enforces that bit must be a zero or one in the circuit.Next, we need to pass an
indicator
bit down to all child statements. This adds support for definition, assignment, for loops, expression, return, and nested conditional statements.