Skip to content

Conversation

@mourner
Copy link
Member

@mourner mourner commented Jun 6, 2019

Closes #38. Closes #39 (being a replacement).

@bontscho I'm very sorry for not getting to your PR in time! Took the same approach but adapted it so that it doesn't rely on Node-specific features, and instead works on typed array level so it works both in Node and the browser. Performance is about the same.

I also opted for doing the optimization by default, without any options — there seems to be no value in turning this off.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6ba4756 on optimize-identical into 8a5683b on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use Buffer.equals as initial comparison for performance gain

2 participants