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 our Call opcode we have a raw integer type representing the Id of the function we want to call. We should avoid a raw integer type for an identifier.
Happy Case
This should be wrapped in a struct type like AcirFunctionId. The type should also be transparent as to not affect serialization.
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:
# Description
## Problem\*
Resolves#5700
## Summary\*
This PR includes an `AcirFunctionId` struct in place of raw integer
identifier in the `Call` opcode to facilitate type safety.
## Additional Context
- The `AcirFunctionId` struct is transparent for compatibility with
serialization.
## 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.
Problem
In our
Call
opcode we have a raw integer type representing the Id of the function we want to call. We should avoid a raw integer type for an identifier.Happy Case
This should be wrapped in a struct type like
AcirFunctionId
. The type should also be transparent as to not affect serialization.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: