This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
feat(acvm)!: update black box solver interfaces to match pwg:black_box::solve
#268
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)
Addresses issue raised in noir-lang/acvm-backend-barretenberg#165
Resolves (link to issue)
Description
Summary of changes
This PR updates all the black box solver functions to accept slices of inputs and outputs rather than wanting a
BlackBoxFuncCall
. This prevents us from having to construct them up in aztec_backend just to feed back into ACVM.As part of this I've updated the
PartialWitnessGenerator
trait to stop passing anoutputs
argument to the range opcode solver as it has no outputs. We could go further and apply similar changes for opcodes with a specified number of inputs/outputs but that felt overkill.Dependency additions / changes
(If applicable.)
Test additions / changes
(If applicable.)
Checklist
cargo fmt
with default settings.Additional context
(If applicable.)