That is true. Moreover, in general the performance of generic code in Go isn't any better than interface-driven one. Generics are there in Go just for better type safety, and IMO that's sufficient already :)
replyIt's all tradeoffs. Fully monomorphized generics tend to blow up compile time.
replyFull monomorphization can also greatly increase code size and icache pressure. Especially if LTO was not possible.
replyI haven’t seen icache pressure causing performance degradation in the wild but it is in theory possible.