Re:Go 1.18
by squeaky-clean on Tuesday March 15, 2022 @10:31PM
(#30694633)
As a non-Go user who peaks into threads about major Go updates, this is one of the most commonly repeated things I've read.
It's a point that's been made repeatedly as comments on this very article.
Re:Go 1.18
by pie_flavor on Wednesday March 16, 2022 @11:59AM
(#30700446)
It's a point that's being made in a different reply chain to the post, in fact.
Re:Go 1.18
by randomdata on Wednesday March 16, 2022 @12:30AM
(#30695331)
I don't know who is saying it, but you can certainly find GitHub repositories of people who have been playing around with generics creating it. Presumably it is people being silly or playing around to see how far they can push the feature under experimental conditions, but developers have also been known to unfathomable things in real code, so I can kind of understand the sentiment. Channels lead to a lot of weird and garbage code when they were new and shiny, when developers felt they should use them for the sake of using them, so the idea isn't unprecedented either.
Who says this? There have been a lot of weird arguments surrounding Go and generics over the last decade, but I’ve never heard anything like this.