Daily reminder: This thread was about concerns that generics would divide Go community. Not about necessity of generics in general.
Two possible scenarios: 1) Go have programmers from very different backgrounds, some used generics often while others never used it. (e.g. Java and C). So different people will use different features of Go with different style and practices. This is the C++ mistake. 2) Go 2 will have such a fundamental new feature and Go 1 programmers will avoid Go 2. To use old code base with Go 2, you have two options; a- Mix Go 1 code with Go 2 code, new code uses generics while old code does not. b- Update Go 1 code to utilize generics. Personally i would rather stay with Go 1. This is the Python mistake. I may be wrong, this is only my concerns. Thanks. -- 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.
