CSE Machine: Avoid pushing unnecessary env instructions (exhaustive version) #1706
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.
Description
This PR aims to implement an exhaustive version of PR #1699 and #1687 .
A
ControlItem
is environment-dependent if its evaluation depends on the current environment, OR its evaluation introduces environment-dependent items onto the control.At each step, if the current control is free of environment-dependent items then we can avoid pushing environment instruction.
Type of change
Some of my concerns
How exhaustive should the logic be? I think it’s enough to cover all node types and instructions allowed to be used in Source. Any remaining node types can default to being environment-independent
I initially wanted to place the logic in the AST file along with statementSeqTransform but I realized the logic needed to work for control items which can be either nodes or instructions. Instructions are only defined within the CSE Machine context so currently I place the logic there.
I modified the test cases to use
generateCSEMachineStateStream
which allows me to check the number of environment-dependent items at each step, but now the test runs synchronously (becausegenerateCSEMachineStateStream
runs synchronously). Would this be a problem?