A lot of it is for me too, but I already do a lot of what it does. I often separate function heads by a newline unless they are very short and are obviously blocked together, and I separate different head types altogether by 2 lines, and categories of functions by 3 lines with a (comment via
##) header then another blank line, which the formatter utterly destroys.
In addition, a lot of the baked tables I use become entirely unreadable. The formatter does some friggin-weird alignment on things like multi-line type declarations and wrapped maps/lists/tuples of things that just push things needless way right (wtf?). A lot of single expression function bodies get formatted very weird out onto multiple lines, making the whole structure horribly unreadable and multi-indentions deep (wtf?). It 'does' format a lot of my sub-blocks inside a function exactly how I already do it, so I like that more people will follow that style (I find it far more readable than what many people do). Overall it seems a good start but it does need some work, especially some way to mark a section as
DO_NOT_FORMAT_THIS as it just breaks some things all to hell that require alignment to be readable, especially data tables, those just become wtf's all around... o.O
Lisp has some very nice formatters, and nicely they work on any lisp style language. ^.^
Really though, if text was not so ubiquitous, editing source via a graph database or something would be awesome, you could make so many useful interconnections and such! Plus IDE's would become practically trivial. ^.^
I will definitely be adding it to my macro string source debug output generation for sure! Convert all that horror of things like
def(blah(x, y), do: 42) into actual usual looking code then! ^.^
I have no qualm with using up lots of space, I like space where it helps readability (like data tables and such), though I would really prefer tabs for indentation and spaces for alignment, always, spaces are not for indentation! o.O!
Yeah this is where I like to put heads together if the functions are very short, and separate by a single blank line if longer (using the same format for all heads of a function).
I do like this aspect of it a lot. ^.^
Yeah I do this same thing here quite a lot (except I had to set it to 3 for some reason that I forgot).
This is what I do!!!
Except for such short functions as you have there they'd have no blank lines between the heads and still have 2 blank lines between the different functions.
I find this style of mine much more readable, and I've been using it across a lot of languages over a lot of years.
Hmm, comments could do the separation I seek, but that would add a lot of noise, especially as I use semantic highlighting in my IDE's so the comments would end up just glowing out of the screen (in semantic highlighting comments are considered as 'way important', if they aren't then you should get rid of them and make the code clearer instead).
I keep up to date with elixir master on my dev server and I have to say that the formatter makes a lot of my code entirely unreadable as it is... I tend to use many short functions when at all possible and pre-generated quick lookup tables and etc, yeesh... ^.^;
Wow that is a lot of work for that, I just do
cd /opt/elixir; git pull; make; _make install... o.O
Although I'm not running different versions here, so eh... I'v not had master elixir break on me yet. ^.^