The "philosophy of gofmt" was to end arguments about how go code should be
Which gives this thread a special form of irony :)
On Mon, Mar 20, 2017 at 1:59 AM, Wojciech S. Czarnecki <o...@fairbe.org>
> > > On Sun, 19 Mar 2017, at 09:35 PM, Rob Pike wrote:
> > > everyone will see code indented as wide (or not) as they prefer.
> > Ian Davis <m...@iandavis.com> wrote:
> > It seems to me that this explanation is at odds with the philosophy of
> > gofmt which is that there is a single way to lay out code.
> > The benefits of that are obvious but using tabs erodes it somewhat when
> > you read code on another computer.
> It is that person who prefers particular tab width who sees code on
> computer. Gofmt makes code 'style' uniform for readability.
> Forced tabs make code familiar with indentation one is
> accustomed to.
> > I always felt the reason for using tabs was to enable support for non-
> > monospaced fonts and multi-width characters. A tab stop in the
> > traditional sense is a linear position, not a number of characters.
> Wojciech S. Czarnecki
> ^oo^ OHIR-RIPE
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.