Go 1.20 Released

Re:Go 1.20 Released by valyala on Wednesday February 01, 2023 @11:55PM (#34622252)

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.

[ Parent | on HN ]

Re:Go 1.20 Released by oauea on Thursday February 02, 2023 @01:09AM (#34622769)

Because it's extremely useful to have adaptable data structures, without byzantine code generation?

[ Parent | on HN ]

Re:Go 1.20 Released by valyala on Friday February 03, 2023 @02:40AM (#34638277)

Could you provide links to a few Go packages, which implement useful generic-based data structures?

[ Parent | on HN ]

Re:Go 1.20 Released by oauea on Friday February 03, 2023 @01:29PM (#34645691)

Try google.

[ Parent | on HN ]

Re:Go 1.20 Released by girvo on Thursday February 02, 2023 @04:03AM (#34624021)

Because they’re not useless.

[ Parent | on HN ]

Re:Go 1.20 Released by valyala on Friday February 03, 2023 @02:40AM (#34638283)

Thanks for very strong argument :)

[ Parent | on HN ]

Re:Go 1.20 Released by girvo on Friday February 03, 2023 @04:13PM (#34647784)

No weaker than yours :)

[ Parent | on HN ]

Re:Go 1.20 Released by vlowther on Thursday February 02, 2023 @10:28AM (#34627844)

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?

[ Parent | on HN ]

Re:Go 1.20 Released by valyala on Friday February 03, 2023 @01:30AM (#34637826)

This sounds good in theory. What about practice? Could you provide a few links to popular Go packages, which benefit from using generics?

[ Parent | on HN ]