Extract ExecutionState
from the Runtime
type
#67
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Runtime
no longer manages the execution state of a guest program. Separating the execution state makes it easier to have a fresh stack for each invocation of an exported function. Also it's now safe to provide a way to accessRuntime
duringHostFunction
execution since no mutable execution state is exposed.Additionally, tests were added to verify the new API surface.