But it would be a subvariant of a much more common pattern in code - destructuring which is quite noisy now but could just be:

  a, b, rest := strings.Split(somestr, "/")

I usually wind up using something like the samber/lo library to reduce the noise here. You wind up doing this all the time.

I must disagree. Destructuring is nifty, but it is almost completely unrelated. The second value in any of the builtin two-value assignment forms is invariant on the type or size of RHS; it's always a boolean, and its meaning relates to the "kind" of RHS, not the exact type:

  msg, ok := <-ch    // ok means "channel ch is not closed"
  val, ok := m[key]  // ok means "map m contains key"
  dyn, ok := i.(T)   // ok means "interface i's dynamic type is T or implements T"

  arr, ok := [N]T(s) // ok means "slice s has len(s) == N"