On Sat, Jun 13, 2020 at 5:37 PM Jake Montgomery <jake6...@gmail.com> wrote:
> You cant really write a short 'end()' function. You have to write an end > function for every type of slice. Or use reflection, which would make the > function slow, and not inlined. Generics anyone? I haven't mentioned anything about the function being universal. IMO in the majority of cases, it does not have to be. Why is such limitation being inserted? It takes probably less time to write the "specialized" end function than we have already spent discussing it. And that's assuming it's a good idea to do so in the first place, which I don't really accept. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAA40n-VbNBCKkbrtwG7mb4GEKmM6OBe_AetPRMG6jAsVf_ULxA%40mail.gmail.com.
