ieee754
ieee754 copied to clipboard
Handling NaN in consistent with Nodejs
This bug eventually leads to this PR.
@feross would you take a look?
@geastwood I haven't looked at this code in a long time. If you wouldn't mind, can you use comments to annotate why each line was changed? I super appreciate it!
Just to bring it in line with nodejs on how to handle NaN and adding a test case for it.
@geastwood Thanks, but I meant line by line. Like, what was wrong with each line, why did you change it?
@geastwood why was this implementation wrong, not Node's?