On this last comment, I would like to comment, Overall I agree with last commenter, the coolest programmer is the one that does not have any quarrels about style, just gets along with the group and helps get the job done.
That being said, golangs approach to braces a part of logical syntax is unusual in comparison to other languages that use braces to encapsulate code blocks. Regarding source control diffs and spaces - I can in fact add loads of spaces and newlines into my go code, and indeed it compiles and it does show up in source diffs. I like spaces in my code in a similar way to how I like to have paragraphs in essays I write. I would argue that everyone likes to use spaces for clarity. Python does not help the argument for the golang style in my opinion, because Python encapsulates code blocks using indent, and just like other languages you are allowed to put your new lines and white spaces wherever you feel it helps. If you like add loads of silly new lines after you conditionals, Python don't care, but pylint does. In python you can alo put your code in a one-liner, or on a new line..., or spread a statement between many lines. So I don't see that Python makes code encapsulation syntactically a part of the conditional syntax like golang does. On Sun, Jul 23, 2017 at 5:12 PM, me <yout...@z505.com> wrote: > > > On Saturday, July 22, 2017 at 4:59:04 AM UTC-6, ohir wrote: >> >> >> Every development team has right to reformat source to their tastes on >> the editor openfile then reformat to compiler taste on savefile. >> > > Except, that some people are minimalists and don't use fancy editors that > have all these bells and whistles... > > I find when you have an editor doing all kinds of tricks, it means the > code is too hard to write and your editor is giving you a warning sign that > what you are doing requires editor tricks, and that's bad. > > For example, if you are making your editor type out the word FUNCTION for > you every time you hit "F" then maybe it would be better to change the > language you are using, to make FUNCTION become "fn" or 'func"... so that > you don't have to have your editor doing so many tricks. > > For the case of GoLang, one thing I do find annoying about gofmt is that > very short IF ELSE blocks span multiple lines.. > > if a > x > else > y > > instead of on a single line. But, that's what gofmt is supposed to stop: > debates about this. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/rzLzp_Z74ik/unsubscribe. > To unsubscribe from this group and all its topics, 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 "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.
