18014398509610716 is an example of such float. When parsed you get 18014398509610720 back because Parser.float internally uses an (Int, Int) representation (before decimal point, after decimal point) and the number above is too large for an Int and loses precision.
An alternative: String.toFloat handles it fine, so I assume there is a (slower? and) more correct way to write Parser.float.
18014398509610716 is an example of such float. When parsed you get 18014398509610720 back because Parser.float internally uses an (Int, Int) representation (before decimal point, after decimal point) and the number above is too large for an Int and loses precision.
An alternative: String.toFloat handles it fine, so I assume there is a (slower? and) more correct way to write Parser.float.