@Alex Besogonov: > Can you provide concrete examples of code that would become more > complicated and/or slower with the addition of generics? I'm > genuinely researching it.
I'm not the one wanting to change the language, it's the other way around. You have to provide concrete examples of why Go needs generics, so far I haven't seen a single real life problem! I haven't seen a single example, including the examples that Ian talks about at GopherCon 2019, that honestly validates adding generics to Go. Even Ian admits that adding generics will make Go much more complex. https://www.youtube.com/watch?v=WzgLqE-3IhY @Ian, for more than 10 years we have managed nicely without generics. The number of times in my 30 years career as a developer I have come across a situation in which I needed a generic solution to some data array etc., is very rare, not something that happens often, and in such rare circumstance I can certainly live with a bit of copy and paste. Furthermore, haven't we already ALL developed all the reverse/sort/whatever Go functions we need for all the different data types? So what is the real true-life problems that validates adding generics to Go? I haven't seen a single example, seriously not one! I have only seen useless examples like the one Ian gives in the talk, which of course I know only serves as an example, but we need real life problems to solve, not theoretical ones. Am I to believe that all the pro-generics people are struggling on a daily basis with copy pasting code all over the place because of sorting, reversing, etc. problems in Go?! Come on already! What I understand from all of this is that people who are pro-generics are in reality really talking about something that is *nice to have*, not something that is seriously needed and this is where I become really frustrated! As I have said many times now, adding stuff to Go comes with a heavy price, it opens the door for all the people who have been whining and complaining about Go for the past ten+ years to add further stuff that is "nice to have", or change things they keep complaining about, like how Go handles errors and what not. After generics gets added, it's going to be something else next time, and again and again. The list goes on and on about changes people want to make to Go. Not real life problems, just so-called "nice to have". No, the added and increased complexity I have witness in other programming languages over the past 3-4 decades, because of exactly things like this, is absolutely mind blowing. This must not happen to Go! -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/17246551608725779%40iva4-6593cae50902.qloud-c.yandex.net.
