On Tuesday, September 20, 2016 at 2:37:29 PM UTC+1, Rupert Smith wrote: > > On Tuesday, September 20, 2016 at 2:08:31 PM UTC+1, Joey Eremondi wrote: >> >> Both int and float end up as a JS number at the end of the day, so >> definitely bounded. Defer to the JS spec? >> > > http://www.w3schools.com/js/js_numbers.asp > > Says "Javascript numbers are always 64-bit floating point". > > Which means a 52-bit mantissa, so ints are bit less than 64-bit... bit of > a bugger as that means where I have used a 64-bit for an object id, I > should really pass as a String and parse into a Data.Integer. Thanks. >
Or just use a String for that case. I can treat all ids as opaque String values. I can probably also user String for big decimals, since the aim would be to capture/display a decimal value such that binary rounding errors are not introduced, rather than to perform arithmetic with them. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" 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.
