←back to thread

Constraints in Go

(bitfieldconsulting.com)
210 points gus_leonel | 1 comments | 17 Nov 24 08:44 UTC | HN request time: 0.2s | source
Show context
indulona ◴[17 Nov 24 09:59 UTC] No.42163167[source]▶
i have been writing Go exclusively for 5+ years and to this day i use generics only in a dedicated library that works with arrays(slices in Go world) and provides basic functionality like pop, push, shift, reverse, filter and so on.

Other than that, generics have not really solved an actual problem for me in the real world. Nice to have, but too mush fuss about nothing relevant.

replies(10): >>42163189 #>>42163244 #>>42163415 #>>42163694 #>>42163834 #>>42164296 #>>42164983 #>>42165141 #>>42165270 #>>42165680 #
1. jppittma ◴[17 Nov 24 14:18 UTC] No.42164296[source]▶
The most frequent use case I and my coworkers run into where we use them is when we want type covariance on a slice.

I.e., when you want to write a function that take some slice of any type T that implements interface I, such that []T is a valid input instead of just explicitly []I.