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

Remove faulty performance comment #76

Closed
wants to merge 1 commit into from

Conversation

BridgeAR
Copy link

@BridgeAR BridgeAR commented Dec 4, 2019

This removes the comment about the performance part (see https://gist.github.com/substack/2790507#gistcomment-3100007).

Instead, recommend to use util.isDeepStrictEqual(), if possible.

This removes the comment about the performance part (see https://gist.github.com/substack/2790507#gistcomment-3100007).

Instead, recommend to use `util.isDeepStrictEqual()`, if possible.
Node's `assert.deepEqual() algorithm` as a standalone module.

This module is around [46 times faster](https://gist.github.com/substack/2790507#gistcomment-3099862) than wrapping `assert.deepEqual()` in a `try/catch`.
Node's `assert.deepEqual() algorithm` as a standalone module. Use `util.isDeepStrictEqual()` in case you use Node.js v9.x or higher and only want the strict comparison.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use { strict: true } for the strict comparison; i think this should be reworded.

@ljharb ljharb marked this pull request as draft September 4, 2023 17:45
@ljharb ljharb closed this in b78de76 Oct 20, 2023
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.

3 participants