I agree that despite genericity is the #1 feature requested by Go
developers in Google's last official survey, there are few chances they
change their mind.
Idem for polymorphism.
So indeed, I've clearly understood that Google and most Go developers don't
care at all about having templating, g
I'm still not convinced that using a language which is especially limited
by design always helps in implementing the simplest solution, that will be
the easiest to maintain.
Maybe it's the case most of the time, but from my personal experience, you
can only get that result by using the right to
2013/9/21, Michael Daconta :
> I assume you say this with tongue-in-cheek; however, I cannot believe
this
> design decision was made. For something to borrow so liberally from C
only
>
> to enforce "one-true" bracing style is frankly ridiculous.
> When someone has coded for a long time usin
As I said, I perfecly understand you decision, and the context in which it
was made.
Anyway, many people here have *strongly* suggested that I must fork the Go
compiler source code and fix it by myself, so I guess I'll have to do it,
and find a way to add a pragma which allows to disable the se
