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
In aztec contracts, unconstrained functions are modified to inject context and abstract their storage. We do this without the need for an annotation.
Aztec #[public] functions are unconstrained, because it's the AVM's role to constrain them. We don't want the user to have to mark every single one of them as unconstrained (also it might give them the incorrect impression that they won't be constrained)
I know this might be controversial (at least the set part), because it might be dangerous if a library author decides to unconstrain certain things and devs don't realize. I've created this to at least have a place to discuss it.
…constrained` (#5962)
…constrained`
# Description
## Problem
Resolves#5954
## Summary
## Additional Context
## Documentation
Check one:
- [ ] No documentation needed.
- [x] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
Problem
In aztec contracts, unconstrained functions are modified to inject context and abstract their storage. We do this without the need for an annotation.
Aztec
#[public]
functions are unconstrained, because it's the AVM's role to constrain them. We don't want the user to have to mark every single one of them asunconstrained
(also it might give them the incorrect impression that they won't be constrained)Happy Case
It's possible to both access:
and modify
a function's runtime in a macro.
Workaround
None
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: