Re: Re: Style Sensitivity
This is awesome. The attempt to avoid endless discussions about
formatting by creating a standard format seems to have actually lead
to more of a discussion of formatting. But I guess it's better that
the discussion is here in the language mailing list, instead of in the
mailing list of every project that ever uses go for decades to come.
The semicolon change has resulted in the enforcement of the bracing
style that was already the standard in gofmt.
If you gofmt your code, then it will compile. Which to me seems
perfectly reasonable for the small minority that will be avoiding the
standard style. Just add gofmt'ing to your make file and forget about
Myself, I've been having great trouble adapting to not putting ()
around my if,for statements, and I'm always putting semicolons at the
end of everything and forgetting the order of name and type in
variable declarations, but I believe given a few months of coding I'll
be used to it.
Since 99% of go code will be in the standard style is seems silly to
add extra hacks to the compiler parser just to accommodate a minority
of code. There are plenty of much more important things for the
developers and the community to worry about(generics,optimisations,
new GC, more library support etc.).
ps. I'd like the bike shed to be purple with pink poker dots because
it brings out my eyes.