-
Notifications
You must be signed in to change notification settings - Fork 20
Unclear & inconsistent formatting. #10
Comments
Hi! The work on the style has not yet been started. In this early alpha phase the aim is to maintain semantic correctness. Once that has been achieved work on the output style can begin. If you like to make an issue each for the string formatting, the function spacing, and for the arrow functions that would be appreciated, thank you! :) |
The first item is a semantic change imo - it's editing the literal text of a comment I entered, putting in \n characters instead. But I agree on the other 2, thanks. I'll check back when the format decisions start happening. |
I'm using semantically the same to mean that they are parsed to the same abstract syntax tree by the Elixir compiler, perhaps I need a better word. :) |
Right. It actually took me a sec to realize that it was turning a triple-quoted string into a single-quoted string, which then made the |
It's because the Elixir parser does this: iex(1)> quote do: """
...(1)> hi!
...(1)> """
"hi!\n"
I plan to fix this, but may take a little while to get there :) |
Here is a comparison of input & output running exfmt on one of my more confusing files. (used exfmt's master as of a few minutes ago)
https://gist.github.com/cschneid/5eb14df36143b6080db5bbb9fee697b5
The text was updated successfully, but these errors were encountered: