2018-05-02



A good blog post by Nomeata about  commas  in  lists.   [0]  IMO,
probably  best  is having trailing commas and such formatting for
multi-line layout:

     {
             foo,
             bar,
             baz,
     }

But this example, he provides, makes sense as well:

     build-depends: base >= 4.3 && < 5
                  , array
                  , deepseq >= 1.2 && < 1.5

... only that I don't like to indent by spaces, thus I would wrap
the lines with a double-indent (two tabs):

     build-depends: base >= 4.3 && < 5
                     , array
                     , deepseq >= 1.2 && < 1.5

By no means is this perfect. Like everything it is a  compromize,
where  I value mechanic indent higher than alignment based on in-
terpreted sentence structure. Reasons are: Indent with only tabs,
mechanical  indent, same indent depth no matter how long the word
``build-depends'' is.

But well, instead of this:

     build-depends: base >= 4.3 && < 5
                     , array
                     , deepseq >= 1.2 && < 1.5

I could also write (with trailing commas allowed):

     build-depends: base >= 4.3 && < 5,
                     array,
                     deepseq >= 1.2 && < 1.5,

Or even better ... and probably best:

     build-depends:
             base >= 4.3 && < 5,
             array,
             deepseq >= 1.2 && < 1.5,

Nothing is more 1TBS than this form.


But well, the question of the leading or trailing comma  is  like
the  positioning  of && and || when breaking lines: At the end of
the previous or at the beginning of the new line. This question I
haven't answered for myself yet ... surprisingly.


[0]  http://www.joachim-breitner.de/blog/739-
Avoid_the_dilemma_of_the_trailing_comma


http://marmaro.de/lue/        markus schnalke <meillo@marmaro.de>