How to create generic method in Go? (method must have no type parameters)

by

You have to declare the slice type with type parameters you want to use for the Map() (or for any other) method:

type slice[E, V any] []E

And you have to add the type parameters to the receiver, without the constraints (those will be the same as defined at the type declaration), as if you’d instantiate the generic slice type:

func (s *slice[E, V]) Map(iteratee func(E) V) *[]V {
    result := []V{}
    for _, item := range *s {
        result = append(result, iteratee(item))
    }

    return &result
}

Testing it:

s := slice[int, string]{1, 2, 3}
m := s.Map(func(i int) string { return fmt.Sprint("x", i) })
fmt.Println(m)

Which will output (try it on the Go Playground):

&[x1 x2 x3]

Also note that slices (slice headers) already contain a pointer to an underlying array, so it’s rare that you need to use a pointer to slice. Instead declare the method with non-pointer receiver, and return a non-pointer (try this one on the Go Playground):

func (s slice[E, V]) Map(iteratee func(E) V) []V {
    result := []V{}
    for _, item := range s {
        result = append(result, iteratee(item))
    }

    return result
}

Relevant section from the (tip) spec: Spec: Method declarations:

If the receiver base type is a parameterized type, the receiver specification must declare corresponding type parameters for the method to use. This makes the receiver type parameters available to the method.

Syntactically, this type parameter declaration looks like an instantiation of the receiver base type, except that the type arguments are the type parameters being declared, one for each type parameter of the receiver base type. The type parameter names do not need to match their corresponding parameter names in the receiver base type definition, and all non-blank parameter names must be unique in the receiver parameter section and the method signature. The receiver type parameter constraints are implied by the receiver base type definition: corresponding type parameters have corresponding constraints.

More Related Contents:

  1. Generic Structs with Go
  2. Pass method argument to function
  3. In Go generics, how to use a common method for types in a union constraint?
  4. generic map value
  5. How can I access a struct field with generics (type T has no field or method)?
  6. Can I construct a slice of a generic type with different type parameters?
  7. How to assign or return generic T that is constrained by union?
  8. Go error: cannot use generic type without instantiation
  9. How to implement generic interfaces?
  10. How can I instantiate a non-nil pointer of type argument with generic Go?
  11. Go Generics – Unions
  12. How to write a generic function that accepts any numerical type?
  13. Difference between any/interface{} as constraint vs. type of argument?
  14. Is there a way to map an array of objects in golang?
  15. How to iterate over a union of slices passed in a generic function? (T has no core type)
  16. Why a generic can’t be assigned to another even if their type arguments can?
  17. Handle maps with same key type but different value type
  18. Sudden Increase in the number of goroutines after upgrade [closed]
  19. cancel a blocking operation in Go
  20. Relative imports in Go
  21. What does (*[1
  22. package’s type cannot be used as the vendored package’s type
  23. How to get the directory of the currently running file?
  24. How to run test cases in a specified file?
  25. Using forked package import in Go
  26. go 1.8 plugin use custom interface
  27. What is a sensible way to layout a Go project [closed]
  28. How can I install a package with go get?
  29. Closing channel of unknown length
  30. Testing a gRPC service

Leave a Comment