-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
doc: reference {set,clear}Immediate in Globals #5830
Conversation
setImmediate/clearImmediate are globals, but not mentioned in the Globals documentation section.
2c6b4ca
to
8a14d93
Compare
LGTM nit: curious if we should include a link to some more in depth documentation on the event loop |
@@ -162,6 +166,21 @@ left untouched. | |||
Use the internal `require()` machinery to look up the location of a module, | |||
but rather than loading the module, just return the resolved filename. | |||
|
|||
## setImmediate(callback[, arg][, ...]) | |||
|
|||
To schedule the "immediate" execution of `callback` after I/O events' |
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 you change "To schedule" to "Schedules".
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.
This is copied verbatum from the timers documentation. If changed in one place should change in another. That alright?
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.
Oh. Yea.
LGTM with one comment. |
|
Preferably what @bengl said imo. |
+1 to @bengl's comment |
@bengl So basically be: ## setTimeout(cb, ms)
See [link to timers markdown] |
@trevnorris Yep. |
Merged #5837, which also solves this. |
setImmediate
/clearImmediate
are globals, but not mentioned in theGlobals documentation section.
R=@nodejs/documentation