3 ms·

Yes but these are release notes for Go 1.20. (1) Make it work, (2) make it right, (3) make it fast They did 1 and 2 in the last two releases, and in Go 1.20 t

Yes but these are release notes for Go 1.20. (1) Make it work, (2) make it right, (3) make it fast They did 1 and 2 in the last two releases, and in Go 1.20 they did (3). So what's left to complain about?

valyala 4y ago
Why to spend time and efforts for adding useless generics in the first place? Maybe it would be better spending this time on performance optimizations, compile times optimizations and binary size optimizations instead.
- oauea 4y ago
  Because it's extremely useful to have adaptable data structures, without byzantine code generation?
  - valyala 4y ago
    Could you provide links to a few Go packages, which implement useful generic-based data structures?
    - oauea 4y ago
      Try google.
- girvo 4y ago
  Because they’re not useless.
  - valyala 4y ago
    Thanks for very strong argument :)
    - girvo 4y ago
      No weaker than yours :)
- vlowther 4y ago
  Because I would rather write one generic container library than n slightly different ones for each data type of deal with screwing around with casting interfaces?
  - valyala 4y ago
    This sounds good in theory. What about practice? Could you provide a few links to popular Go packages, which benefit from using generics?