-
Notifications
You must be signed in to change notification settings - Fork 292
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A small refactoring of the EccOpQueue to make it safer to use. Work includes: Closes AztecProtocol/barretenberg#891 Closes AztecProtocol/barretenberg#899 - Updating access specifiers on members and methods to make the API safer, e.g. no direct access to ultra_ops, raw_ops etc. - Explicitly connecting ultra_ops and raw_ops so that both are updated simultaneously by a small set of well defined methods. They can no longer be updated independently. - Addition of some `..._for_testing()` methods to replace cases where members that are now private were being accessed directly in tests. Its still nice to have these for failure testing etc but it is no longer possible to create bad witnesses without them (unless the API methods become incorrect). Note: I've changed the method `empty_row()` to `empty_row_for_testing()` since it has no practical use aside from testing. I'm not sure who added this originally. It might be better to just delete it altogether but given the recent confusion over ECCVM tests passing when they shouldn't I figured we can take all the testing avenues we can get. `ClientIVCBench/Full/6 22893 ms 17742 ms 1`
- Loading branch information
1 parent
1eb288e
commit 822c7e6
Showing
17 changed files
with
271 additions
and
242 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.