Computations currently require a message and a transaction context. This is because, up until EOF, computations were built from a message with transaction-like fields. This PR opens support for computations that do not come from messages. One such example will be an EOF computation which is built from instructions in the bytecode of a message computation.
How was it fixed?
To make way for the above changes, the BaseComputation class is refactored in this PR to be more basic. It strips out the the idea that all computations rely on a message. This is now a property of the MessageComputation class that we are more familiar with, which is still configured as part of all VMs at present, and inherits from and builds upon the BaseComputation.
This PR does not attempt to add any new computation classes. It is simply paving the way for them by splitting the current BaseComputation class into these two classes.
Todo:
[x] Clean up commit history
[x] Add or update documentation related to these changes
What was wrong?
Related to Issue #2089
Computations currently require a message and a transaction context. This is because, up until EOF, computations were built from a message with transaction-like fields. This PR opens support for computations that do not come from messages. One such example will be an EOF computation which is built from instructions in the bytecode of a message computation.
How was it fixed?
To make way for the above changes, the
BaseComputationclass is refactored in this PR to be more basic. It strips out the the idea that all computations rely on a message. This is now a property of theMessageComputationclass that we are more familiar with, which is still configured as part of all VMs at present, and inherits from and builds upon theBaseComputation.This PR does not attempt to add any new computation classes. It is simply paving the way for them by splitting the current
BaseComputationclass into these two classes.Todo:
Cute Animal Picture