Is your feature request related to a problem? Please describe.
As of now, when an optional value is retrieved via .get() a corresponding state transition is emitted. Problem is that this state transition respects the isSome of the value retrieved, so when the value is none then the state transition from is also none. This is a problem since the state transition prover then ignores the from of the state transition.
Describe the solution you'd like
The correct way to issue state transitions anchored to the previous state, is to mark the from as some instead of none. This applies to all cases including .get() and .set() state transitions
Additional context
This issue was discovered during the PR review of #7
Is your feature request related to a problem? Please describe. As of now, when an optional value is retrieved via
.get()a corresponding state transition is emitted. Problem is that this state transition respects theisSomeof the value retrieved, so when the value is none then the state transition from is also none. This is a problem since the state transition prover then ignores the from of the state transition.Describe the solution you'd like The correct way to issue state transitions anchored to the previous state, is to mark the from as some instead of none. This applies to all cases including
.get()and.set()state transitionsAdditional context This issue was discovered during the PR review of #7