Harry Sarson

The issue is that this number (`1000000000000000000000` or `0x36_35C9ADC5_DEA00000`) requires more than 64 bits to represent. Elm format changes it to `3875820019684212736` or `0x35C9ADC5_DEA00000`, truncating it to the least significant...

What if elm-format did not try to encode literals as Int's in the AST but kept all literals as strings? This way there would be no encoding issues.

I would prefer to see elm-format raising a parsing issue rather than silently corrupting* source code files. Alternatively, if elm-format left big integer literals as they are there would be...

Related https://github.com/avh4/elm-format/issues/635

> It's really not easy to use some editor feature to do it, compared to other expressions like lists, tuples, lambdas... Would a find and replace from `->\n` to `->`...

> I like the feature for case expressions though So do I!

I think that adding parentheses is more useful where the operator precedence is potentially confusing. For example: ```elm True || False && False || False ``` gives `True` as it...

The binaries get stripped before deployment which is why you do not see any backtrace info. Backtrace should be more informative if you ran with a locally built version of...

The only really interesting thing here at this point in time (and the reason I am putting this PR out) is the `LexItem` datastructure https://github.com/elm-in-elm/compiler/blob/a2164213a49b51bbc72e5729db97ca692e583083/src/Stage/Parse/Lexer.elm#L8-L73 Thoughts on these custom types...

In my experience of elm/parser parser, the most painful thing is understanding what the _state_ of parser is when it fails. The parser 1. kindly spits out the location of...