IssueRaiser

Note that this is "broken" in a very tiny way, which is unlikely to cause any real-world problems in code which uses floating-point corre...

Note that this is "broken" in a very tiny way, which is unlikely to cause any real-world problems in code which uses floating-point correctly, i.e. does not rely on its exactness (or lack thereof.) It's not like with integers, where e.g. 1000000 becoming 999999 or 1000001 would be a severe bug. If you're interested in the details of floating-point maths, the rest of the site has other fascinating articles too. Converting strings to and from floating-point correctly in all cases turns out to be quite a tricky thing to do in practice.

Posted by userbinator on Jun 20, 2015, 3:18 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments

reliability (Other)

Note that this is "broken" in a very tiny way, which is unlikely to cause any real-world problems in code which uses floating-point corre...

userbinatorJun 20, 2015, 3:18 PM

Note that this is "broken" in a very tiny way, which is unlikely to cause any real-world problems in code which uses floating-point correctly, i.e. does not rely on its exactness (or lack thereof.) It's not like with integers, where e.g. 1000000 becoming 999999 or 1000001 would be a severe bug. If you're interested in the details of floating-point maths, the rest of the site has other fascinating articles too. Converting strings to and from floating-point correctly in all cases turns out to be quite a tricky thing to do in practice.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue