New Merge function.

I noticed you’ve changed how the merge function works. You now use an array instead of an object:

var target = []

Then when you use it, you also use a for in loop:

for (var i in merge(lastValue, nextValue))

For in loops with arrays are notorious for various unexpected issues and are known for not being very performant compared to alternative means of looping Stackoverflow, The Problems with for…in and JavaScript Arrays. I’d suggest using map instead. It’s more performant, easier to read and doesn’t suffer from issues that for of can cause:

merge(lastValue, nextValue).map(nextValue => {
  var style = nextValue == null || nextValue[i] == null ? "" : nextValue[I]
  //...
})

This is just a friendly suggestion, not an OMG we gotsa have it!

[rbiggs]

See, that’s the whole thing about JSPerf. It makes it really easy to put together misleading tests. One thing, if you are going to use JSPerf to determine an architectural direction, you really need to test on as many browsers as possible: IE11, MSEdge, Firefox, Chrome and Safari. Browsers optimize different things, resulting in sometimes wildly different results for the same perf.

[jorgebucaran]

A new version is out! Thanks, @rbiggs, for discovering my mistake.