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
The Aztec team has been leaning heavily in a custom data type called BoundedVec that is an attempt to mock slice/vec functionality using arrays, where essentially you can add to a Vec but that Vec has a max capacity.
Happy Case
Move BoundedVec into the stdlib for those who would like to use more complex slice/Vec logic.
# Description
Partially resolves#4020.
Need to then remove from `aztec-packages` and move to this
implementation.
## Problem\*
Resolves <!-- Link to GitHub Issue -->
## Summary\*
## Additional Context
## Documentation\*
Check one:
- [ ] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[Exceptional Case]** Documentation to be submitted in a separate
PR.
# PR Checklist\*
- [ ] I have tested the changes locally.
- [ ] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
---------
Signed-off-by: Kevaundray Wedderburn <kevtheappdev@gmail.com>
Co-authored-by: vezenovm <mvezenov@gmail.com>
Problem
The Aztec team has been leaning heavily in a custom data type called BoundedVec that is an attempt to mock slice/vec functionality using arrays, where essentially you can add to a Vec but that Vec has a max capacity.
Happy Case
Move
BoundedVec
into the stdlib for those who would like to use more complex slice/Vec logic.Copy the BoundedVec implementation from https://github.com/AztecProtocol/aztec-packages/blob/1c8ea497fb1d64da64cb240917a60d57bd1efef8/yarn-project/noir-protocol-circuits/src/crates/types/src/utils/bounded_vec.nr#L1
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: