You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Problem
We duplicate assertion messages for all Brillig calls that are inserted from generated brillig into our generated ACIR
noir/compiler/noirc_evaluator/src/ssa/acir_gen/acir_ir/generated_acir.rs
Line 593 in 19ffa20
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
The text was updated successfully, but these errors were encountered: