Re:Generics can make your Go code slower
by pphysch on Wednesday March 30, 2022 @03:08PM
(#30859522)
You're right, here's what one of my hot loops look like:
func (cc *ComponentContainer[T]) ForEach(f func(*Component[T])) {
for _, page := range cc.pool.pages {
for i := range page {
if page[i].IsActive() {
f(&page[i])
}
}
}
}
Still, the interface approach is a total nightmare from a readability + runtime error perspective so I won't be going back & will just hope for some performance freebies in 1.19 or later :^)Just to clarify things here: a pointer receiver on a generic type isn't what was covered in the article. That was covering if your `T` is a pointer type.
If T here is a value-type, you're probably getting monomorphization (at the cost of copying the value all over, and possible benefit of inlining to reduce that copying).
Thanks, that makes more sense!
My components are all small structs (coordinates, states, health values, etc) so I am happy to copy them around
Component[T] is something like
{
Metadata_fields...
Data T
}
On this basis, I don't believe your generic implementation is as faster than an interface implementation as you claim.