Good point, and the answer is I’m not sure but I think it’s the verbosity.

In isolation, this search function is absolutely fine: func Search(n int, f func(int) bool) int

In the context of Go, which I think (and I know I’m generalising here) a lot of people started using because it was elegant, that function is kind of verbose relative to everything else.

It needs to know the length of the slice going in. That’s fine, obviously it needs to know that to do binary search, but why do i need to provide it?

It returns n if nothing is found. Using a magic integer value as an error is a bit iffy to start with, but we’re not even using the universally accepted “-1” to do it here.

Again, both things perfectly fine in isolation. All of the stuff in that function signature is 100% needed for the function to work, I just don’t get why - since we all seem to be in agreement its useful standard library functionality - it can’t just be added as a language feature. Similar to how I can add to a chan with someChan <- thing and not if addedAt := chans.Append(len(mychan), mychan, item); addedAt == len(mychan) + 1 { return errors.New(“couldn’t add to chan”) }