It's error-prone to have to write WithContext all the time.
context stack makes the situation even more complex.
Proposal
Since the current design is to satisfy the StateDB interface, we can make a StateDB struct on the fly inside the ApplyMessage, and the keeper is clean from the mutable states, and pass the ctx around in the keeper methods.
yihuang
commented
3 years ago
The States
ctxStackstateErrThe problem
WithContextall the time.Proposal
Since the current design is to satisfy the
StateDBinterface, we can make aStateDBstruct on the fly inside theApplyMessage, and the keeper is clean from the mutable states, and pass thectxaround in the keeper methods.