4 ms·
I had a runtime TYPE error not too long ago. Integers in elm are a lie. I got scientific notation for a float back when an integer went over the limit of javasc
by boxed 6y ago
I had a runtime TYPE error not too long ago. Integers in elm are a lie. I got scientific notation for a float back when an integer went over the limit of javascript floats.
It was a stupid bug on my part that numbers got that big obviously but still. Take the no runtime errors with a grain of salt.
- wolfadex 6y agoDid you try out https://package.elm-lang.org/packages/cmditch/elm-bigint/latest/ https://package.elm-lang.org/packages/cmditch/elm-bigint/lat...? I've used that for things that I know exceed the browsers limits with JS numbers. Had to use it recently with something that returned a JS BigInt (which was a whole other buggy problem).
- boxed 6y agoThe problem with that is that by the time you have a problem it's too late. Python has real integers that don't overflow. Elm does not.