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
Zac's asked for benchmarks on brillig vs native compiled rust in order to determine the feasibility of implementing significant cryptographic algorithms in pure brillig.
We should add benchmarks comparing various sample programs compiled in brillig vs native rust to track execution speed.
The text was updated successfully, but these errors were encountered:
# Description
## Problem\*
Related to #5101
## Summary\*
Add the number of brillig opcodes in the info command
## Additional Context
## Documentation\*
Check one:
- [X] No documentation needed.
- [ ] 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.
---------
Co-authored-by: Maxim Vezenov <mvezenov@gmail.com>
Zac's asked for benchmarks on brillig vs native compiled rust in order to determine the feasibility of implementing significant cryptographic algorithms in pure brillig.
We should add benchmarks comparing various sample programs compiled in brillig vs native rust to track execution speed.
The text was updated successfully, but these errors were encountered: