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

Do not duplicate assertion payloads for Brillig functions #5792

Open
vezenovm opened this issue Aug 22, 2024 · 0 comments
Open

Do not duplicate assertion payloads for Brillig functions #5792

vezenovm opened this issue Aug 22, 2024 · 0 comments
Labels

Comments

@vezenovm
Copy link
Contributor

Problem

We duplicate assertion messages for all Brillig calls that are inserted from generated brillig into our generated ACIR

for (brillig_index, message) in generated_brillig.assert_messages.iter() {
.

Happy Case

Similarly to our deduplication of Brillig bytecode with the BrilligCall opcode and Brillig debug locations we should also deduplicate the Brillig assertion payloads so to not repeat them as part of ACIR.

We should note though that assertion payloads are included as part of the Circuit struct and resolved using that. This is necessary for ACIR but we should be able to split out unconstrained functionality. Either way, this is a breaking serialization change.

Workaround

Yes

Workaround Description

No response

Additional Context

No response

Project Impact

None

Blocker Context

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant