Editorial: Remove unnecessary checks for undefined before ToPositiveInteger #2332
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.
ToPositiveInteger(undefined)
callsToIntegerThrowOnInfinity(undefined)
, which in turn callsToIntegerOrInfinity(undefined)
, which in turn callsToNumber(undefined)
.ToNumber
returnsNaN
,ToIntegerOrInfinity
then returns0
,ToIntegerThrowOnInfinity
returns0
unchanged, and finallyToPositiveInteger
will throw a RangeError for0
. That means it's not necessary to handleundefined
before callingToPositiveInteger
.Split from #2265.