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
Because get_counter is first elaborated within the comptime increment call, the value for COUNTER within it gets locked in as a constant - the current value of that constant which is 1 when it is first called. When it is later mutated and get_counter is called again, the value was inlined as a constant so the value is still 1 when it should be 2.
To Reproduce
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
No response
NoirJS Version
No response
Proving Backend Tooling & Version
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#5991
## Summary\*
Fixes two issues:
1. The original linked issue where elaborating a function early would
cause any globals to be "locked in" in a sense.
2. The fact that we were never actually mutating underlying values in
the interpreter.
## 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.
Aim
Expected Behavior
The program to execute without error
Bug
Fails with:
Because
get_counter
is first elaborated within the comptimeincrement
call, the value forCOUNTER
within it gets locked in as a constant - the current value of that constant which is 1 when it is first called. When it is later mutated and get_counter is called again, the value was inlined as a constant so the value is still 1 when it should be 2.To Reproduce
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
No response
NoirJS Version
No response
Proving Backend Tooling & Version
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: