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
{{ message }}
Repository navigation
refactor(AztecMacro): Improve detection of compute_note_hash_and_nullifier #4647
#4610 autogenerates fn compute_note_hash_and_nullifier unless the user has already provided an implementation. However, we're checking for the user to provide an implementation with the exact right number and type of parameters. If they e.g. forget one, or get a type wrong, we'll stil try to declare our autogenerated version, resulting in a duplicate definition error.
We should emit more useful errors in this scenario, e.g. point out that the user-defined function is wrong.
changed the title [-]Improve detection of compute_note_hash_and_nullifier[/-][+]refactor(AztecMacro): Improve detection of compute_note_hash_and_nullifier[/+]on Mar 8, 2024
Activity
feat!: autogenerate compute_note_hash_and_nullifier (#4610)
[-]Improve detection of compute_note_hash_and_nullifier[/-][+]refactor(AztecMacro): Improve detection of compute_note_hash_and_nullifier[/+]feat!: autogenerate compute_note_hash_and_nullifier (#4610)
feat!: autogenerate compute_note_hash_and_nullifier (#4610)
nventuro commentedon Jun 2, 2025
Stale - this fn is now a contract library method, and there's no need for a user to provide it.