Based on what I've seen, the implementation of generics *may* slow down the compilation.
See https://github.com/golang/go/issues/49569. On Wednesday, February 23, 2022 at 5:50:52 PM UTC-7 Jason E. Aten wrote: > There was nothing in the tutorial, and I see that the design declines to > commit, permitting "the implementation to decide", per > https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#implementation > > So I was just curious which way the implementation ended up going. > > On Wednesday, February 23, 2022 at 2:41:14 PM UTC-6 Jason E. Aten wrote: > >> Back in 2009, Russ wrote a blog on generics, talking about the tradeoffs >> in providing generics: >> >> "The generic dilemma is this: *do you want slow programmers, slow >> compilers and bloated binaries, or slow execution times? " -- * >> https://research.swtch.com/generic >> >> I haven't had the bandwidth to follow the generics detailed discussions. >> I was just curious, at a high level, for creating a mental model of Go's >> generics: which approach was taken? >> >> Thanks! >> >> J >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/43f4fed8-effb-4480-8b82-313a33d261afn%40googlegroups.com.
