disallow reentrancy#380
Draft
arnetheduck wants to merge 1 commit into
Draft
Conversation
Member
Author
|
Marked draft to merge into 4.0 |
zah
reviewed
May 23, 2023
| doAssert not loop.polling, "The event loop and chronos functions in general are not reentrant" | ||
|
|
||
| loop.polling = true | ||
| defer: loop.polling = false |
Contributor
There was a problem hiding this comment.
I believe Chronos already needs to wrap every call to user-land in try/except, so why is it not possible to just set this flag there, just before entering user-land?
arnetheduck
force-pushed
the
no-reenter
branch
from
088e6af to
f5dbbbd
Compare
arnetheduck
force-pushed
the
no-reenter
branch
2 times, most recently
from
c41575c to
50abdc4
Compare
Reentrancy causes event reordering and stack explosions, in addition to leading to hard-to-debug scenarios. Since none of chronos is actually tested under reentrant conditions (ie that all features such as exceptions, cancellations, buffer operations, timers etc work reliably when the loop is reentered), this is hard to support over time and prevents useful optimizations - this PR simply detects and disallows the behaviour to remove the uncertainty, simplifying reasoning about the event loop in general.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reentrancy causes event reordering and stack explosions, in addition to leading to hard-to-debug scenarios.
Since none of chronos is actually tested under reentrant conditions (ie that all features such as exceptions, cancellations, buffer operations, timers etc work reliably when the loop is reentered), this is hard to support over time and prevents useful optimizations - this PR simply detects and disallows the behaviour to remove the uncertainty, simplifying reasoning about the event loop in general.