Comment #3 on issue 3738 by [email protected]: Inconsistent rounding in
float parser
https://code.google.com/p/v8/issues/detail?id=3738
Attempting to figure out why some `toFixed(..)` results appeared to round
and others didn't, I went about trying to implement the spec as faithfully
as I could. This is what I ended up with:
https://gist.github.com/getify/652f1f58ca3a13bd29e4
Of course, I may be missing something, but I think it's faithful to the
spirit of the spec. And notably, for `1.15`, it gives "1.2", not "1.1".
My test case btw was 859.385. I think the problem I am seeing is exactly
the same as being discussed in this thread.
So, is the algorithm I presented, specifically the 10.a part where the `n`
is selected, just untenable for engines to implement?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
