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.
There is some further optimization in mind including optimizing the states and there is some regression since I do not include the code for detecting whether there is any call rn. Once the state optimization is included I believe this will be resolved anyway.
I also want to remove resumeValue and instead have the runtime modify the saved locals directly as that seem to cause quite some amount of excessive code.
The current approach mandates the use of the lifter. As lifter can not handle semantics of handle blocks (and it does not need to), we lower handle block to an equivalent form first, without the insertion of effect checks/resumption prelude. Now we invoke the lifter after handle block is translated and before the actual instrumentation takes place. We make use of the fact that lifter will preserve the mayRaiseEffect field.
For stack safety, I simplified the approach taken in #307, since we always include the entry state and we do not need to split into different cases when stack safety is enabled.