Use prototype based Recorder for performance boost.

[jamestalmage]

The current method of creating a PowerAssertRecorder prevents some optimizations by the V8 compiler.

Specifically, it creates many extra closure contexts, and prevents the use of hidden classes.

My test suite was seeing roughly a 5% boost.

[jamestalmage]

Why can't this just be source: args? I did it this way to mimic what you had before, but I am not entirely sure why it's necessary to create a safe copy of args here.

[twada]

Yeah it's redundant. source: args would be better. Renaming args would be more better :)

[jamestalmage]

OK. Working on this now. It takes a while to update all the "expected" fixtures

[twada]

Thanks!!

[jamestalmage]

done!

[jamestalmage]

@twada -

The function.toString() seems it to make it easier to edit the helper template. The only issue is it prevents coverage using nyc because of this. It really only seems to be an issue while I was trying to npm link this into ava (the solution was explicitly excluding **/babel-plugin-espower/** in my nyc config).

An alternate solution (should you ever want to add code coverage to this project), would be to move the helper to it's own file and just use fs.readFileSync.

[twada]

@jamestalmage Nice optimization!
Just out of curiosity, is function.toString() portable enough?

fs.readFileSync approach looks better to me.

[jamestalmage]

fs.readFileSync added 😄

[jamestalmage]

@twada - should be good to go

[twada]

@jamestalmage Looks good to me. I'm going to merge and cut a new release.

[twada]

@jamestalmage babel-plugin-espower 2.1.1 is out. Thanks!