Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

benchmark: util._extend vs object.assign #7255

Closed
wants to merge 4 commits into from
Closed

benchmark: util._extend vs object.assign #7255

wants to merge 4 commits into from

Commits on Jun 10, 2016

  1. benchmark: util._extend vs object.assign 

    To copy the values of all enumerable own properties from-
a source object to a target object, node still use-
`util._extend`, though newer standard `Object.assign`
is available. This is because `util._extend` is found to
be faster than `Object.assign`. This benchmark test is
to keep track of how performance compare.
    @suryagh
    suryagh committed Jun 10, 2016
    Configuration menu
    Copy the full SHA
    a74addc View commit details
    Browse the repository at this point in the history

Commits on Jun 11, 2016

  1. benchmark: review comments

    @suryagh
    suryagh committed Jun 11, 2016
    Configuration menu
    Copy the full SHA
    100a8be View commit details
    Browse the repository at this point in the history

  2. benchmark: use proxy object as target

    @suryagh
    suryagh committed Jun 11, 2016
    Configuration menu
    Copy the full SHA
    a3daa3b View commit details
    Browse the repository at this point in the history

Commits on Jun 20, 2016

  1. benchmark: use proxy object as target 

    fixed spacing nit.
    @suryagh
    suryagh committed Jun 20, 2016
    Configuration menu
    Copy the full SHA
    0e9260f View commit details
    Browse the repository at this point in the history