util: fix comment typos
When the deep(Strict)Equal comparison functions were moved to an internal module, a variable named `current` was replaced with `val1`. That accidentally also replaced a few "currently"s in comments. Refs: https://github.com/nodejs/node/pull/16084 PR-URL: https://github.com/nodejs/node/pull/21436 Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Weijia Wang <starkwang@126.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
This commit is contained in:
parent
193d6d1bda
commit
686cb4dbd0
@ -287,7 +287,7 @@ function setHasEqualElement(set, val1, strict, memo) {
|
||||
return false;
|
||||
}
|
||||
|
||||
// Note: we val1ly run this multiple times for each loose key!
|
||||
// Note: we currently run this multiple times for each loose key!
|
||||
// This is done to prevent slowing down the average case.
|
||||
function setHasLoosePrim(a, b, val) {
|
||||
const altValues = findLooseMatchingPrimitives(val);
|
||||
@ -381,9 +381,9 @@ function findLooseMatchingPrimitives(prim) {
|
||||
}
|
||||
|
||||
// This is a ugly but relatively fast way to determine if a loose equal entry
|
||||
// val1ly has a correspondent matching entry. Otherwise checking for such
|
||||
// currently has a correspondent matching entry. Otherwise checking for such
|
||||
// values would be way more expensive (O(n^2)).
|
||||
// Note: we val1ly run this multiple times for each loose key!
|
||||
// Note: we currently run this multiple times for each loose key!
|
||||
// This is done to prevent slowing down the average case.
|
||||
function mapHasLoosePrim(a, b, key1, memo, item1, item2) {
|
||||
const altKeys = findLooseMatchingPrimitives(key1);
|
||||
|
Loading…
x
Reference in New Issue
Block a user