My primary concern about generics is they may significantly hurt build times, which coming from C++ I am rather sensitive about. Beyond that I am worried that they might end up NOT being an improvement over all the tools that have already popped up to handle this problem. There are a lot of ways to generate code for Go already that can be run once and checked into your source repo. Regenerated if you need to support a new type or fix a bug. This is very reasonable and rational IMHO. I have yet to have a significant issue with this approach, outside of tooling phobia. Even in languages with prolific template support, I have often ended up eschewing them for better, external text processing tools. I think Mike Acton has something useful to add to the conversation about avoiding templates in C++: https://youtu.be/rX0ItVEVjHc?t=1h11m19s Questioner: ...you're against templates... how do you deal with code duplication?... Mike Acton: ... templates, how do you remove code duplication? One, it is almost certainly not as big a problem as people think it is. They invent things to duplicate so they can invent templates to solve the problem. But in the cases where it is potentially useful you can also generate the code. A template is just a poor man's text processing tool, we have tons of stuff that processes text, you can actually do a really great job with some other tool that does it better. You don't need templates in order to solve that problem... /mytwocents
-- 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.
