| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The common case is where setTimeout() is called with two arguments, the callback and the timeout. Specifying optional arguments in the parameter list forces common case calls to go through an arguments adaptor stack frame. PR-URL: nodejs#1221 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
The common case is where setInterval() is called with two arguments, the callback and the timeout. Specifying optional arguments in the parameter list forces common case calls to go through an arguments adaptor stack frame. PR-URL: nodejs#1221 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
It turns out we have little to no test coverage for setTimeout() and setInterval() calls with optional arguments. Now we do. PR-URL: nodejs#1221 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
|
LGTM Aside: Thought the penalization was mostly fixed (so that the performance difference was essentially white noise) in V8 for calling a function with too many parameters. My bad for not catching that before it was pushed. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The common case is where setTimeout() is called with two arguments,
the callback and the timeout. Specifying optional arguments in the
parameter list forces common case calls to go through an arguments
adaptor stack frame.
R=@trevnorris?