feat: Add Proof mode Initialization & Loop #120
Draft
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.
Closes #134, #135
Builtins initialization: in proof mode, all builtins of the layout are initialized but only the ones used by the program are appended to the stack.
Specific stack initialization:
end
segment must be populated with a JumpRel 0 instruction.Introduces a
RunnerMode
enum for different initialization steps depending on the run context.The different checks (builtins usage, range_check, memory and diluted pool) have been inline in a single method
checkCellsUsage()
, which returns a boolean whether they passed for the chosen layout.