René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should `nextTick` and timers accept context or parameters?","articleBody":"Currently, both timers and `nextTick` only take a callback argument (and some timers take a duration argument).\n\nIt is beneficial to pass additional arguments and/or the context to timers. The io.js code base is littered with code like:\n\n``` js\n  var self = this;\n  process.nextTick(function() {\n    self.emit('close');\n  });\n```\n\nIt's possible to either pass a context (`this`) to these functions or to pass arguments like the DOM version does making the above:\n\n``` js\n  process.nextTick(function() {\n     this.emit('close');\n   }, this);\n```\n\nOr:\n\n``` js\n  process.nextTick(function(element) {\n     element.emit('close');\n   }, this);\n```\n\nThis can make cleaner code and save closure allocations - it also isn't slow like `.bind`. \n\nWas this proposed before? \n\nI realize the Timers API is locked (`nextTick` is not afaict) but I'm wondering how people feel about this.\n","author":{"url":"https://github.com/benjamingr","@type":"Person","name":"benjamingr"},"datePublished":"2015-02-25T11:34:18Z","url":"https://github.com/nodejs/node/issues/953"}