The new parser cannot parse scientific notation floating point numbers

[gilramir]

For example, in gren-lang/test/src/Test/Distribution/Internal.gren

a1 : Float
a1 =
    -3.969683028665376e1

results in:

 % ../gren.sh format --pre-ast gren-lang/test/src/Test/Distribution/Internal.gren
-- FAILED TO PARSE ---------- gren-lang/test/src/Test/Distribution/Internal.gren

223| a1 : Float
224| a1 =
225|     -3.969683028665376e1
                            ^
226|
227|

Not a valid number

[gilramir]

And, for "gren format" to be able to faithfully write the number in the way the author wrote it, the AST will have to record if the float was written in decimal or scientific notation.

[gilramir]

Oh, one more comment. I originally hit this not because of the example above, but because the source file I was trying to format had a "small" decimal-notation floating point in it. I don't remember exactly, but something like 0.0000000001

"gren format" wrote the formatted version in scientific notation, because String.toFloat uses a javascript function which will render small-value floating points in scientific notation.

In "gren format" I added a routine to print the decimal version of a floating point, to avoid String.toFloat.

We might need that type of function in a new function of String.
Or maybe we just store the original text of the floating point in the AST, so no matter which tool is consuming the AST, the original string representation of the floating point is available.

[gilramir]

I'll handle this.
Besides numbers, do you want the parser to honor Nan and Inf as special floating point values?

[gilramir]

I'm awful at linking github PRs with github issues... the PR with the first draft is #22

[gilramir]

BTW, @robinheghan , this can be closed now; the solution was merged in issue 22, not linked to issue 21 because I didn't write a good enough commit message for github