-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
assert,util: improve comparison performance #61176
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
Open
BridgeAR
wants to merge
3
commits into
nodejs:main
Choose a base branch
from
BridgeAR:BridgeAR/2025-12-26-faster-comparison
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
assert,util: improve comparison performance #61176
BridgeAR
wants to merge
3
commits into
nodejs:main
from
BridgeAR:BridgeAR/2025-12-26-faster-comparison
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes sure that the toStringTag symbol is used, if available instead of calculating the toString() value each time, if not needed (the type checks make a brand check, so there is no need to check the toStringTag, if non is defined on the object).
Member
Author
|
Local benchmark |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #61176 +/- ##
=======================================
Coverage 88.52% 88.52%
=======================================
Files 703 703
Lines 208585 208612 +27
Branches 40225 40240 +15
=======================================
+ Hits 184650 184674 +24
- Misses 15953 15957 +4
+ Partials 7982 7981 -1
🚀 New features to boost your workflow:
|
This is a workaround for errors recreated by error serdes.
Contributor
aduh95
reviewed
Dec 27, 2025
| } | ||
| } else if (mode === kLoose && | ||
| (isFloat32Array(val1) || isFloat64Array(val1) || isFloat16Array(val1))) { | ||
| (isFloat32Array(val1) || isFloat64Array(val1) || isFloat16Array(val1))) { |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unrelated change (we should probably have the linter enforce one or the other)
Suggested change
| (isFloat32Array(val1) || isFloat64Array(val1) || isFloat16Array(val1))) { | |
| (isFloat32Array(val1) || isFloat64Array(val1) || isFloat16Array(val1))) { |
cjihrig
approved these changes
Dec 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
needs-benchmark-ci
PR that need a benchmark CI run.
needs-ci
PRs that need a full CI run.
util
Issues and PRs related to the built-in util module.
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.
This makes sure that the toStringTag symbol is used, if available instead of calculating the toString() value each time, if not needed (the type checks make a brand check, so there is no need to check the toStringTag, if non is defined on the object).