Skip to content

process: nextTick should not be handled lazily #3860

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.

Sign up for GitHub

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

Closed
yorkie wants to merge 4 commits into from
Closed

process: nextTick should not be handled lazily #3860

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
29d8578
process: nextTick should not be handled lazily
yorkie Nov 16, 2015
250e4a1
fix nits
yorkie Nov 17, 2015
c3961db
fix nits
yorkie Nov 17, 2015
3a4b6af
fix nits
yorkie Nov 17, 2015
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
Prev Previous commit
Next Next commit
fix nits
  • Loading branch information
@yorkie
yorkie committed Nov 17, 2015
commit c3961dbfe23cf3edf015b12d500bf666ab331ba5
4 changes: 2 additions & 2 deletions src/node.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -486,11 +486,11 @@
}

function nextTick(callback) {
if (typeof callback !== 'function')
throw new TypeError('callback is not a function');
// on the way out, don't bother. it won't get fired anyway.
if (process._exiting)
return;
if (typeof callback !== 'function')
throw new TypeError('callback is not a function');

var args;
if (arguments.length > 1) {
Expand Down