From ea7487401afc9cdc92030e9c20246bf5f8e8a7a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9e=20Kooi?= Date: Wed, 20 Jun 2018 15:10:56 +0200 Subject: [PATCH] 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 --- lib/internal/util/comparisons.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/internal/util/comparisons.js b/lib/internal/util/comparisons.js index 119fb66611a7c6..f4491f070f18d6 100644 --- a/lib/internal/util/comparisons.js +++ b/lib/internal/util/comparisons.js @@ -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);