Avoid unbounded stack consumption for synchronous control flow #96
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.
Previously, as sequence of state transitions that did not pass through an
asynchrous boundary incurred stack frames. The trivial loop in the enclosed
test case would then overflow the stack.
This commit merges the
resume
andapply(tr: Try[Any])
methods into aapply
. It changes the body of this method to be an infinite loop withreturns at the terminal points in the state machine (or at a terminal
failure.)
To allow merging of these previously separate matches, states that contain
an await are now allocated two state ids: one for the setup code that calls
onComplete
, and one for the code in the continuation that records theresult and advances the state machine.
Review by @phaller / @danarmak