Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/guides/timers-in-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,11 +94,11 @@ some major ways they differ. The first is that `process.nextTick()` will run
*before* any `Immediate`s that are set as well as before any scheduled I/O.
The second is that `process.nextTick()` is non-clearable, meaning once
code has been scheduled to execute with `process.nextTick()`, the execution
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps...

Refer to [this guide][../topics/the-event-loop-timers-and-nexttick#processnexttick]
to better understand the operation of `process.nextTick()`.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, sounds good.

cannot be stopped, just like with a normal function. Although the function
passed to `process.nextTick()` will be run synchronously, it will execute
outside the current call stack.
cannot be stopped, just like with a normal function. Take a look at [this guide]
(../topics/the-event-loop-timers-and-nexttick#processnexttick) to better
understood how `process.nextTick()` is executed.

### "Déjà vu" Execution ~ *`setInterval()`*
### "Infinite Loop" Execution ~ *`setInterval()`*

If there is a block of code that should execute multiple times, `setInterval()`
can be used to execute that code. `setInterval()` takes a function
Expand Down