Let’s not do participation trophies though, Pike and Thompson were the original authors of Go. Both of them should know better. It’s fine to include an ineffic

Let’s not do participation trophies though, Pike and Thompson were the original authors of Go. Both of them should know better. It’s fine to include an inefficient version if you also have a ‘proper’ way to fall back to when performance does matter. And if performance does not matter, why are you even using Go? Funnily enough Python Ruby and Node do expose performant ways to do this in the stdlib, so...