I'm curious: are there use-cases where template generation with gengen/genny/etc are not enough? seems to me that calling "go generate" a few times (when you need to generate generic containers for certain types) is a very fair tradeoff to have generic containers without having to change the language core (or possibly affecting build times for all the other cases that don't need them).
On Sat, Jul 29, 2017 at 1:04 PM, Robert Melton <rmel...@gmail.com> wrote: > > On Sat, Jul 29, 2017, at 12:36, dogan.k...@dodobyte.com wrote: > > I was watching rus cox's last talk > <https://www.youtube.com/watch?v=0Zbh_vmAKvk> and he mentioned that not > every problem should be solved by language change. Some can be solved by > tooling or library change. > > I am curious has any of the generics lovers written a tool that helps for > generic behavior. Something like,* > > > There are a bunch https://github.com/taylorchu/generic, https:// > github.com/cheekybits/genny, https://github.com/joeshaw/gengen, and > https://github.com/clipperhouse/gen and I am sure many more that I don't > have sitting in my bookmarks. > > Also, building a basic one yourself if you don't want to use those tends > to be exceptionally straightforward. > > -- > Robert Melton | rmel...@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. > -- "Worse things happen at sea, you know!" -- 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.
