2 ms·
Personally, I'm waiting until 1.19 to start seriously exploring generics. By then, the dust will have settled a bit, folks will have some good lessons learned
by candiddevmike 5y ago
Personally, I'm waiting until 1.19 to start seriously exploring generics. By then, the dust will have settled a bit, folks will have some good lessons learned to share, and there may be more packages in the stdlib for generics.
- ainar-g 5y agoI feel like a lot of people will wait (although perhaps not up until 1.19) for the simple reason that tooling support is still not quite there yet. See [1] and the related issues. Static code analysis is reasonably popular in Go projects, and just disabling all failing tools until the tooling is there is not something most people would agree to, I think. With that said, of the tools that I use about ⅔ are already reasonably compatible. Unfortunately, the other ⅓ are among the most essential ones. [1]: https://github.com/golang/go/issues/48525 https://github.com/golang/go/issues/48525
- bashery 5y ago+1
- thegeekpirate 5y agoPlease stop posting this on every comment you agree with, as you're not adding anything useful to the discussion, while also sending alerts to people for no good reason. Click on the upvote button instead.