> On Thursday, May 24, 2012 at 1:09 PM, Paul Borman wrote:

> So with something like:

> <TAB>if value, err := something.Method(buffer, source); err == nil &&
> value == 17 {
> <TAB><TAB>code
> <TAB>}

> you would end up with

> <TAB>if value, err := something.Method(buffer, source); err == nil &&
> <TAB>                                                   value == 17 {
> <TAB><TAB>code
> <TAB>}

> ?

> On Thu, May 24, 2012 at 1:00 PM, Kevin Ballard <kball...@gmail.com> wrote:

> On Thursday, May 24, 2012 at 8:32 AM, Paul Borman wrote:

> Do forget other cases:

> } else if A && B ... {

> if statement; A && B ... {
> }

> And so on.  There coud be an entire heuristics paper on how best to format
> these things.  I agree the current gofmt solution is not optimal, however,
> having a single sub-optimal solution beats multiple "optimal" solutions.
>  With gofmt I know what to expect when reading code.   (And even BSD vs GNU
> go code would look the same with gofmt, oh the horrors!)

> The solution I'm proposing still fits here. Just one rule: "continued
> conditionals on subsequent lines are indented (with spaces) to match the
> start location of the conditional on the first line". This should cover all
> the cases.

> On Thursday, May 24, 2012 at 2:17 AM, Reynir Reynisson wrote:

> Some people might use a three space wide tabstop.

> Then those people can live with having their conditionals visually line up
> with the body of their scope.

> Either we use >1 tab (or tap + spaces) to indent subsequent lines, which
> looks awful for everybody, or we use a solution that looks good for nearly
> everybody but the occasional person with weird settings has a slightly
> sub-optimal experience (and honestly, their experience would just be the
> same as everybody else's is today).

> -Kevin

>     -Paul

> On Thu, May 24, 2012 at 8:23 AM, Norbert Roos <nr...@webware-experts.de>wrote:

> On 05/24/2012 11:17 AM, Reynir Reynisson wrote:

> if conditionA&&
>    conditionB&&
>    conditionC&&  {
> bodyOfStatement()
> }

> Some people might use a three space wide tabstop.

> ... which would result in

> if conditionA&&
>   conditionB&&
>   conditionC&&  {
>   bodyOfStatement()
> }

> Norbert