News for hackers. Stuff that matters.

A comment on How generics are implemented in Go 1.18. Parent comment

Re:How generics are implemented in Go 1.18 by socialdemocrat on Wednesday March 02, 2022 @04:34AM (#30525499)
Nah… if so was embracing C# style complexity I would rather do Swift of Rust. At least they have a clean solution for fixing the million-dollar-mistake.

My chief attraction to Go is simplicity. I can be away from Go for years and pick it up again really fast. With simplicity, you naturally need to make some sacrifices, but I think Go team has been diligent about choosing those.

[ Parent | on HN ]
Re:How generics are implemented in Go 1.18 by kerkeslager on Wednesday March 02, 2022 @10:48AM (#30528618)
> Nah… if so was embracing C# style complexity I would rather do Swift of Rust.

Just so we're clear here, you're using the word "complexity" to describe the situation of not having to copy paste or `go generate` 30 different implementations of the same class for different types because your language lacks generics.

[ Parent | on HN ]