feat(nargo): Remove usage of CompiledProgram
in CLI code and use separate ABI/bytecode
#1269
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.
Related issue(s)
Resolves #
Description
Summary of changes
This PR removes the usage of
CompiledProgram
from the interface of the interface of the internal CLI functions, instead we pass ABI and bytecode separately.Using
CompiledProgram
doesn't really make sense anymore as now we havePreprocessedProgram
so we need to explicitly create aCompiledProgram
from the ABI and bytecode to pass it into a function where they'll be split again.As part of this I've removed
verify_cmd::verify_proof
as it didn't really do much other thannargo::ops::verify_proof
Steps 1 and 3 can instead be delegated to the caller, at which point they can just call
nargo::ops::verify_proof
themselves.Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Documentation needs
Additional context
This would also be required if we were to support performing actions against contract functions in nargo (as these are not represented as
CompiledProgram
s