`parse_float` in JavaScript seems too strict about stdlib HOT 4 CLOSED

As a note, it does behave the same on erlang:

3> binary_to_float(<<"1">>).
** exception error: bad argument
     in function  binary_to_float/1
        called as binary_to_float(<<"1">>)
        *** argument 1: not a textual representation of a float
4> binary_to_float(<<"1.0">>).
1.0

from stdlib.

... which is used by gleam on erlang
https://github.com/gleam-lang/stdlib/blob/main/src/gleam/float.gleam#L36
https://github.com/gleam-lang/stdlib/blob/main/src/gleam_stdlib.erl#L167-L171

from stdlib.

With the current impl float.parse then on case of Error then int.parse
https://github.com/gleam-lang/stdlib/blob/main/src/gleam/int.gleam#L107 and then int.to_float on case of Ok https://github.com/gleam-lang/stdlib/blob/main/src/gleam/int.gleam#L292

from stdlib.

This is the intended behaviour. The JavaScript float parsing function is not a design we have copied.

from stdlib.