While the example of ReverseSlice doesn't appear in my work experience, the concept of writing functions for slices independent of type is pretty common for me.
Not having to copy to/from []someInterface or having to write (or go generate) multiple versions of the code differing only on the type would allow me to delete quite a bit of code. On Wed, Dec 23, 2020, 23:35 Martin Hanson <greencopperm...@yandex.com> wrote: > Oh, I almost forgot, it also clearly does not "have minimal impact on > everybody else", which is another proposal selection criteria. Go code > becomes much more complex to read and understand from all the examples I > have seen. > > You can even find several YouTube videos with people trying to analyze and > understand the Go generics code in the examples, and they are all > struggling. > > -- > 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/910771608795256%40sas8-ed615920eca2.qloud-c.yandex.net > . > -- 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/CAEX6X_B__7QpYSEG_gyp8aWnmjnpM5M-GmdfBp3Mw7mDiY5xeg%40mail.gmail.com.
