Petka Antonov

.each forms a chain of the promises in the array that behaves exactly like a normal manually formed promise chain. With long stack traces the entire chain is always kept...

There are some conflicts

It means you should ditch the benchmark.js library and just use our own runner. I am just gonna hook it to the release script, so that it runs every time...

it has been some year after I last ran the benchmark but for me it used to give same result every time

After some point the results suddenly start being ~270ms in every run, so something probably happened with your computer. Ignoring them, all the "time" results are within ~6% of the...

"Mems" are even more stable, every result within ~3% of the average. So I guess 10-15% and 5-10% deviations respectively should give some warning that benchmark needs to be run...

Test doesn't seem to pass?

Seems like it requires a major bump

Agree with spion that we should keep the old behavior and only throw if nothing but single immediate function value is passed

There is no reason to break existing code because the docs only mention the old usage at the end as side note so the risk of new code using the...