Can we please, collectively, decide that this thread serves no productive purpose anymore and abandon it? The only thing it is doing is inviting ad-hominem attacks and hostile behaviors from all sides of the debate. No matter where you stand on this, please abide by the spirit of the community CoC <https://golang.org/conduct> to create a warm, welcoming community where people can enjoy participating. This question, no matter how invested you are in it, isn't worth giving that up for it. (yes, I know I don't always do that myself. Please call me out, if I do).
Please be excellent to each other :) On Sun, Jul 30, 2017 at 2:06 PM, <ecstatic.co...@gmail.com> wrote: > Personally I'd prefer a simple compiler option :) > > On Sunday, July 30, 2017 at 12:50:55 AM UTC+1, Hrobjartur Thorsteinsson > wrote: >> >> Dude, you are right. This confusing coding style with syntax in Go can be >> fixed by forking and applying a rediculously small patch. Jeez, lets stop >> complaining as u rightfully suggested. >> >> 29. júl. 2017 10:43 e.h. skrifaði "Wojciech S. Czarnecki" < >> oh...@fairbe.org>: >> >>> On Sat, 29 Jul 2017 10:36:42 -0700 (PDT) >>> ecstati...@gmail.com wrote: >>> >>> [APM] >>> [Ad Personam mode on, I humbly apologize to bystanders] >>> >>> Enough is enough! >>> >>> > 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. >>> >>> This is yours strictly personal affair. Through this all thread you >>> *demand* >>> from the go team and the community to design, write and maintain tools >>> for >>> functionality *only you personally* deem important. More - you *demand* >>> from >>> us __thousands and millions of hours of compile time__ because *you* want >>> your tastes satisfied. >>> >>> Stop whining and *do instrument* your editor with s/(\S\s*)}\s*$/\1\n}/. >>> In C++ or java or ecmascript or... >>> It is You who need this style so make your environment allow it. Its >>> easy. >>> (It was common in times we were paid by LOC but had 22 usable screen >>> lines). >>> >>> If above instrumentation is beyond your allman-loving team competence why >>> and *HOW* do you want to program anything usable to others? >>> >>> > All that because maybe 2 or 3 languages designers have decided so, >>> > moreover to make it easy to automatically add the semi-colons. >>> >>> They gave it to you for free. It is open source. So >>> >>> *FORK* >>> >>> Tailor to your tastes! Make ponies dance! >>> >>> > 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. >>> >>> *FORK* !!! Do better. >>> >>> [\APM] >>> >>> -- >>> Wojciech S. Czarnecki >>> << ^oo^ >> OHIR-RIPE >>> >>> -- >>> 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/to >>> pic/golang-nuts/rzLzp_Z74ik/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> golang-nuts...@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. > -- 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.
