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.
Problem
When a fiber encounters a child fiber/promise to wait on during execution,
IOTask
currently resumes the parent in a newIOTask
instance after the child completes. Besides the performance cost, this makes the identity of a fiber not stable since it might be executing in a linkedIOTask
instance if it got suspended by a child fiber. It's a blocker to implement fiber trace dumps for example since the actual execution trace might in a linkedIOTask
instance.Solution
Adapt the logic to simply resume the
IOTask
after a child completes and the execution of the parent needs to resume.