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.
This patch exposes the current loop state as
loop.state
. I find myself repeatedly needing to read the loop state in many circumstances, so I usually create astate
variable, but then I need to keep the loop state in sync with that variable and I need to pass around both objects all over the place. One recent example is to get browserify-hmr working well with main-loop, I need to trigger a loop update with the current state unchanged. With this patchloop.update(loop.state)
will do the trick.One caveat is that people might try writing to this value instead of calling
loop.update()
but I added a note to the docs to say not to do that.If nothing else, you can cherry-pick 0b534b5 to get more API docs without the other state-exposing changes.