Skip to content
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

Fixes _.isNaN for wrapped numbers #2259

Merged
merged 2 commits into from
Aug 4, 2015
Merged

Fixes _.isNaN for wrapped numbers #2259

merged 2 commits into from
Aug 4, 2015

Conversation

debutt
Copy link

@debutt debutt commented Aug 3, 2015

fixes #2257

@debutt
Copy link
Author

debutt commented Aug 3, 2015

Looks like the linter won't allow the use of !=.

@paulfalgout
Copy link
Contributor

why not just //eslint-disable-line eqeqeq?

@debutt
Copy link
Author

debutt commented Aug 3, 2015

Using the native isNaN achieves the same goal, and, cleaner code : )

@paulfalgout
Copy link
Contributor

Perhaps. This issue does seem to go back and forth a lot: 2dff99d

@debutt
Copy link
Author

debutt commented Aug 4, 2015

Back to square one lol. I think it's a matter of how they define the behavior of the function.

@michaelficarra
Copy link
Collaborator

This LGTM.

megawac added a commit that referenced this pull request Aug 4, 2015
Fixes _.isNaN for wrapped numbers
@megawac megawac merged commit 0b16f58 into jashkenas:master Aug 4, 2015
@jdalton
Copy link
Contributor

jdalton commented Aug 4, 2015

Looks like the bug was introduced with the linting rules.

@michaelficarra
Copy link
Collaborator

Whoops, my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

_.isNaN returns true for whatever created with new Number() instead of just NaN and new Number(NaN)
5 participants