Ten Years of “Go: The Good, the Bad, and the Meh

Re:Ten Years of “Go: The Good, the Bad, and the Meh by icholy on Tuesday July 18, 2023 @12:18PM (#36774935)

> Nevertheless I think people implementing them in their own projects is basically code smell and they are a symptom of poorly thought-out code rather than excellent code.

Who needs data structures right?

[ Parent | on HN ]

Re:Ten Years of “Go: The Good, the Bad, and the Meh by Veraticus on Tuesday July 18, 2023 @12:42PM (#36775391)

Uh, generics are not data structures and generics are neither the only way nor the best way to interact with data structures.

[ Parent | on HN ]

Re:Ten Years of “Go: The Good, the Bad, and the Meh by lillywastaken on Tuesday July 18, 2023 @06:03PM (#36779684)

Do you think it is somehow more elegant to have a specialised version of a data-structure for every single type that may need to be placed into it? Or just to ignore the type whatsoever and erase it via interface{}? Even Golang's designers obviously realise that generics are a better way to interact with data structures because the standard types map and array were always "generic", just special cased as such.

[ Parent | on HN ]

Re:Ten Years of “Go: The Good, the Bad, and the Meh by lenkite on Wednesday July 19, 2023 @01:12PM (#36789837)

Yeah, you must hate use the golang map type then. It is a generic data-structure.

[ Parent | on HN ]