Comment #40 on issue 3006 by [email protected]: Inaccurate sin/cos values
http://code.google.com/p/v8/issues/detail?id=3006
This change revealed several problems with D3's geographic features, such
as winding order determination for spherical polygons. (There is
necessarily a discontinuity when the area of a spherical polygon is zero.)
For example:
https://github.com/mbostock/d3/issues/1753
https://github.com/d3/d3-geo-projection/issues/10
I expect these problems would disappear if the suggestion in #38 were
accepted, but I need to investigate whether how to workaround the new
behavior in D3 to know for sure.
I raise this to illustrate how seemingly minor changes to these essential
functions can cause unexpected problems downstream. We can likely fix D3 to
avoid the problems, but it would be nice to provide stronger guarantees on
expected behavior (e.g., sin(x) = x for x in [-1e-7, 1e-7]).
--
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/groups/opt_out.
