Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port UltraComposer changes to UltraPlonkComposer and UltraHonkComposer #378

Closed
codygunton opened this issue Apr 24, 2023 · 0 comments
Closed
Assignees

Comments

@codygunton
Copy link
Collaborator

codygunton commented Apr 24, 2023

With #366 merging soon, we are ready to refactor all of the composers in plonk in to split out circuit construction functionality. To do this development incrementally, @Rumata888 has created FooPlonkComposer for Foo in {Standard, Turbo, Ultra}, since the composer interface will change.

In the meantime, some changes have gone into UltraComposer to support NounsDAO builders. We need to make sure these changes are reflected in the refactor.

@ledwards2225 ledwards2225 mentioned this issue May 4, 2023
11 tasks
lucasxia01 pushed a commit to AztecProtocol/aztec-packages that referenced this issue Sep 25, 2023
At some point during the great composer split, a couple of tests that
depended on new builder functionality from Zac were not passing. I
confirmed that all of the functionality referenced in bberg issue No 378
has been ported to the one and only `UltraCircuitBuilder` and the
previously disabled tests now pass.

Note: the tests have been reordered a bit which makes the diff a bit
funny but they are largely unchanged. I combined two tests into one
since they were highly connected and made minor syntactic changes to get
them up to date with the rest of the codebase.

Closes bberg issue No.
[378](AztecProtocol/barretenberg#378)

# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
@ledwards2225 ledwards2225 self-assigned this Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants