-
Notifications
You must be signed in to change notification settings - Fork 9
Define 'tick' #141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define 'tick' #141
Conversation
* | ||
* One iteration of the loop is called one "tick". A tick covers the following steps: | ||
* | ||
* 1. Activate watchers created / enabled in the last tick / before `run`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With `run` you are referencing the method? Please suffix ()
then to make this more obvious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
* 1. Activate watchers created / enabled in the last tick / before `run`. | ||
* 2. Execute all enabled defer watchers. | ||
* 3. Execute all due timers, each timer only once per tick. | ||
* 4. Execute actionable stream watchers, each only once per tick. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh, there is no order guarantee between timers and stream watchers. Merge these two into a single step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, once per tick should be fine?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that's fine.
* | ||
* 1. Activate watchers created / enabled in the last tick / before `run()`. | ||
* 2. Execute all enabled defer watchers. | ||
* 3. Execute all due timer and actionable stream callbacks, each only once per tick. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can signals be executed at any time or should they be included in this step? All current implementations execute pending signals only in this step, but should that be part of the spec?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, they should. Missed that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed.
No description provided.