I understand you now. On Sat, Jul 29, 2017 at 10:36 AM <ecstatic.co...@gmail.com> wrote:
> Sorry to repeat myself, but I think I wasn't clear enough, as many people > on this forum still don't understand my point at all. > > Google, as ANY company, MUST force its employees to use exactly the same > standards. > > I've done the same with the engineers in my company. And they used my own > code formatting tool. > > And I'm glad to Google that their management decided to let us use their > compiler and their other internal tools, including Gofmt. > > But as Gofmt can ALREADY enforces this common coding style, and can be run > at any time, including before committing code on the depots, why should it > be enforced by the COMPILER too ? > > Really, that's the one particular engineer decision I regret. Just one. > But that's a big one. Because sometimes, almost ENTIRE teams prefer the > Allman style. That's not just a personal affair. All that because maybe 2 > or 3 languages designers have decided so, moreover to make it easy to > automatically add the semi-colons. > > And it doesn't even work well, we are now force to put a useless comma > after the last parameter of a function to be allowed to split the arguments > on several lines. Please don't insult me by telling there wasn't any other > possible solution. > > > For instance, in Javascript, the semi-colon are also optional, but the > compiler lets you use whatever coding style you want. > > You can then use a tool like Gofmt to fix it automatically. There is one > such tool on my github account btw. > > On Friday, July 28, 2017 at 6:14:01 AM UTC+1, Ian Lance Taylor wrote: > >> On Thu, Jul 27, 2017 at 6:35 PM, Hrobjartur Thorsteinsson >> > <thorste...@gmail.com> wrote: >> > >> > Do you realize that the Go lang devs themselves are not actually in >> > agreement about the original motivations for constraining the language >> in >> > this way. Some quote some one true K&R style, while it is in fact this >> is >> > not K&R style, other quote some dubious statistics on programmer >> habbits >> > with code blocks, and yet other quote that it's just to help the >> Go-lang >> > compiler meta-compile statement delimiters ";". All this confusion and >> > effort for nothing, and all the while ignoring some real bad >> programming >> > habits, I guess in the name of liberty... or one day they will >> eventually >> > arbitrate what is good and bad in those areas too. >> > >> > Could it be that Go lang devs created an inflexibility, a storm in a >> > tea-cup, for no real good reason. Such things have happened in software >> > before. >> >> I doubt there is any significant disagreement among the core Go >> developers about the gofmt choices for brace placements. The reasons >> are 1) it doesn't matter, gofmt just has to make a choice; 2) the >> choice works well with lexical semicolon insertion. >> >> Ian >> > -- > 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. > -- Michael T. Jones michael.jo...@gmail.com -- 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.
