Talk:Currency: Difference between revisions

→‎Problem with tasks examples?: Updated my implementation
(→‎Problem with tasks examples?: Updated my implementation)
Line 10:
:Possibly we could introduce a need for an exact comparison that would fail under floating-point? I agree about keeping it draft for now. --[[User:TimToady|TimToady]] ([[User talk:TimToady|talk]]) 16:07, 3 January 2014 (UTC)
::Good points. I had thought of this but didn't have a good idea for how to do it. I really didn't want to make arbitrary precision a requirement as I think that's overkill in almost all cases. I also didn't want to explicitly ban floating point, but how's this for a compromise?. It's kind of contrived to land numbers in the range where 64 bit floats don't quite work but 64 bit ints still do. I added 15 zeros to the 4 (and changed the shake price so improper rounding would still show up.) —[[User:Sonia|Sonia]] ([[User talk:Sonia|talk]]) 21:25, 4 January 2014 (UTC)
::: The numbers are (necessarily) more foolish now, but the test is a good one anyway. In particular, there's now plenty of places to go wrong if you're not careful… –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 22:48, 4 January 2014 (UTC)
Anonymous user