slides/go-generics.md at main - slides - Mills – I’m presenting this tomorrow at work, something I do every Wednesday to teach colleagues about Go concepts, aptly called go mills() 😅

Well actually today rather, today is ready tomorrow 🤣 Damn i need to go to bed 😴

@prologic@twtxt.net That’s a cool concept! I’d love to have that at work, too.

When introducing generic functions you switched the parameter s to be the slice and not the element to search for. Maybe keep it consistent with the rest of the code samples and change s and x to xs and s. Or even better, use nicer names. :-)

Also, you might want to tell a few sentences about the ~. When I first encountered underlying types I was a bit puzzled.

Keep up the great Go talks!

@prologic@twtxt.net In part two, you can talk about generic types. ;-) I used them here the first time: https://git.isobeef.org/lyse/tt2/-/blob/master/ui/treeview/treeview.go

So. Some bits.

i := fIndex(xs, 5.6)

Can also be

i := Index(xs, 5.6)

The compiler can infer the type automatically. Looks like you mention that later.

Also the infer is super smart.. You can define functions that take functions with generic types in the arguments. This can be useful for a generic value mapper for a repository

func Map[U,V any](rows []U, fn func(U) V) []V {
  out := make([]V, len(rows))
  for i := range rows { out = fn(rows[i]) }
  return out
}


rows := []int{1,2,3}
out := Map(rows, func(v int) uint64 { return uint64(v) })

I am pretty sure the type parameters goes the other way with the type name first and constraint second.

func Foo[comparable T](xs T, s T) int

Should be

func Foo[T comparable](xs T, s T) int

Yhanks for the feedback @lyse@lyse.isobeef.org and @xuu 👌 It was late at night and I made a few minor errors despite reviewing twice 😆

@xuu I see a walrus!

@chunkimo@twtxt.net lol. go walrus!!