This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
Keep witness
argument immutable on halo2_mock_prover
#175
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 #170
On the SuperCircuit's
halo2_mock_prover
method, we are currently overriding thesuper_witness
dict object.Initially it holds the
TraceWitness
objects of each internal circuit, but after the loop it holds the JSON representation of the witness of the circuit.Since the elements in the dict are indexed by their
rust_id
, after the loop all the elements have been replaced, leaving the caller ofhalo2_mock_prover
with a "modified"witness
.It's not a big problem, but it's confusing sometimes when writing tests, if you want to verify some of the assignments, because the order of lines becomes relevant.
I didn't add the return of the
witness_json
because so far I've seen no use for it. Maybe it could be interesting.