Reduce allocations in compile loop by reusing context object

[punkpeye]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Problem

In the compile function, a new object is created via Object.assign for every event in the token stream:

while (++index < events.length) {
  const handler = config[events[index][0]]

  if (own.call(handler, events[index][1].type)) {
    handler[events[index][1].type].call(
      Object.assign(
        {sliceSerialize: events[index][2].sliceSerialize},
        context
      ),
      events[index][1]
    )
  }
}

This can result in thousands of object allocations. These short-lived objects create GC pressure, which shows up as garbage collection pauses in CPU profiles.

Current solutions

N/A

Proposed solutions

Since sliceSerialize is the only property that varies per event, we can reuse a single context object and mutate just that property.

[wooorm]

Sounds interesting, but it would be nice to have profiling numbers.
Mutating may leak memory / be hard to type right!

[punkpeye]

I don't see any benchmark in the repo. Is there none?