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.

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

Why is this 2x the size of mixin-deep? #7

Open
doublemarked opened this issue Jun 27, 2018 · 2 comments
Open

Why is this 2x the size of mixin-deep? #7

doublemarked opened this issue Jun 27, 2018 · 2 comments

Comments

@doublemarked
Copy link

Is there any functional difference between,

  // 3.5Kb
  result = mergeDeep(obj1, obj2)

  // 1.1Kb
  result = mixinDeep({}, obj1, obj2)
@jonschlinkert
Copy link
Owner

From the readme:

image

@doublemarked
Copy link
Author

doublemarked commented Jul 13, 2018

@jonschlinkert I saw that, but it doesn't answer my question. I believe the examples I wrote above demonstrate how you can use either library to accomplish the same behavior as mergeDeep, but mixinDeep is 1/3 the size.

Is there any functional difference between those two lines I wrote?

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

No branches or pull requests

2 participants