Use performant Object.create replacement #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Object.create
is much slower than using thenew
operator in some versions of V8 (confirmed in Chrome 33 using V8 3.23, see this jsperf). This changes calls toObject.create()
to a semantically-equivalentcreateObject()
helper function that creates objects using a constructor function and thenew
operator.This change also adds a basic benchmark script that can be run in node using
npm run bench
or served to the browser usingnpm run bench-server
.My benchmarks before the change:
And after the change: