DomenicDenicola/qunit — comment on commit 6f9ff2f49ac6ba001f96bbe83336b0b5b83724f8
File:  line 0
By prathe:

The implementation of your request is precise. Good work.

In your case you would consider both objects to be the "same", but they aren't because one have a constructor and the other not. The philosophy behind deepEqual was to not making any assumptions and say that two values are different as soon as there is a way to prove they are.

But I guess we could do an exception in that case. I've looked for how this could break some use cases, but I could not find any. For myself I think I would not have use Object.create(null), but just a regular object not to change the codebase, but that is maybe because I've never tweaked objects with Object.create.

My conclusion is that I don't think you pull request will hurt anything. If you find it practical there are some others that will find it practical too. I think we should live with it.