Benchmarks

[lemire]

Simple benchmark to check that the performance can be good. (You should run this yourself.)

[SalvatorePreviti]

Hello, didn't have time before to check or reply, had some work to do and I was concentrated in completing the AVX2 + SSE4 support that is now available in version 0.2.5.

Is very good to have a benchmark, and I really like it and the way this is done. Would like to integrate it.

However, is there a particular reason to create a separate npm package?
Usually to do benchmarks I create a benchmark.js in the ./scripts folder that would not be published together with the npm package. I would then add a "npm run benchmarks" in package.json that can be run when you do a git pull of the repository.
Is there a particular reason to have a separate package?

Thanks :)

[lemire]

Is very good to have a benchmark

I would recommend building a benchmark you like, running it and posting your results in the README so people know whether it is fast.

However, is there a particular reason to create a separate npm package?

Just convenience. There are dependencies. You have to import these dependencies. I don't really care.

You can throw away this PR, doesn't matter to me. You may want to build from it, however.

[SalvatorePreviti]

Sure, tomorrow will pull this and do some commits. The dependencies are fine if kept in devDependencies. Thanks :)