> A lot of people consider code gen a second class solution when compared to a more traditional generics implementation. I don't think so. Code generation can be very effective. No major concerns about indecipherable error messages. When in doubt you can inspect the generated code to understand exactly what is the problem.
It's an interesting fact that when go gen was introduced, proponents of go gen on this very forum were swearing that it wasn't designed to be a solution for generics. Code gen to make up for a lack of a feature in a type system will always be like building an half baked language on top of another. Code generation will never replace polymorphism at compile time. -- 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.
