Use !== instead of equivalent < #2
Open
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.
Here's the current code:
I noticed with the prior guard on line 3, the condition on line 6 can be
!==
, rather than<
. In Ye Olde Days, we used to expect that'd be faster.I'm usually seriously skeptical of "microbenchmarks", especially in interpreted languages like JavaScript. But since the whole point here is perf, I thought I'd pass along, so you can make the choice.
Feel free to drop this one.