“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”
― Bjarne Stroustrup, I use other programming languages too - obviously. And I will continue to think of better ways to perform Go, if not complaining. Meanwhile this <https://github.com/dc0d/goreuse> is a tool to write generic code in Go, employing code generation (that I wrote) - not waiting for day dreams to come true and instead get done with the job. This was just some thought sharing. Especially the last two form - the generic Method Expression and the interface one - if they be a single-type-parameter type of generics, are interesting to investigate. Like if we could write: type method func (*) append(n int, m anotherConcreteType, prev *) type comparer interface { (*) compare(*) } None of these mean that Go has to change - while it might, a bit - but brain teasers. On Friday, February 16, 2018 at 3:45:33 PM UTC+3:30, M P r a d e s wrote: > > Have a look at Rust, Ada or even C++, they all have some form of generic > programming and are fast or faster than Go. Bonus, none of these use > garbage collection. > > Don't hold your breath with Go getting any substantial changes in its type > system. Move on. > > Developers should use tools that suit them, not tools that force > developers to adapt them. > -- 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.
