Skip to content

Add node-independent shim for global setImmediate()#663

Merged
sokra merged 6 commits intomasterfrom
add/setimmediate
Jan 10, 2015
Merged

Add node-independent shim for global setImmediate()#663
sokra merged 6 commits intomasterfrom
add/setimmediate

Conversation

@jhnns
Copy link
Copy Markdown
Member

@jhnns jhnns commented Jan 6, 2015

As discussed in #419

Btw: Why is the console shim deactivated by default?

@jhnns
Copy link
Copy Markdown
Member Author

jhnns commented Jan 6, 2015

It's failing on node 0.11 because of a missing sandbox...

@jhnns
Copy link
Copy Markdown
Member Author

jhnns commented Jan 7, 2015

Can now be merged.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Does it make sense to have node.setImmediate and node.clearImmediate?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I was wondering about that too, butsetImmediate and clearImmediate are imho closely linked together. You wouldn't want to specify individual options for that. If there's a setImmediate it needs a clearImmediate as well. And since you always think of setImmediate and barely need clearImmediate I decided to call it setImmediate.

sokra added a commit that referenced this pull request Jan 10, 2015
Add node-independent shim for global setImmediate()
@sokra sokra merged commit 16777f6 into master Jan 10, 2015
@sokra
Copy link
Copy Markdown
Member

sokra commented Jan 10, 2015

Thanks

@sokra sokra deleted the add/setimmediate branch November 6, 2015 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants