Actually, this isn't too bad. Given Go already flips types and names in
syntax, having the generic specification in front of the entity it
decorates doesn't seem too alien looking. The too-mang-() concern has
already brought up to the draft, I think it likely require some careful
thinking... production code could be way more complicated than trivial
examples, I hope bringing generics wouldn't kill the elegant looking and
simplicity of Go code in large...
On Monday, June 22, 2020 at 9:46:56 AM UTC-7, redst...@gmail.com wrote:
>
> I read the new generic draft. And I know F<T>,F[T],F《T》 is discarded. I
> think put the type paremeter in front of the function name may be better.
> No ambiguous and more readable code.
>
> func Print(type T)(s []T) {}
>
> Print(int)([]int{1, 2, 3})
>
> func <type T>Print(s []T) {}
>
> <int>Print([]int{1, 2, 3})
>
>
>
--
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/cf511869-052e-4964-a9c6-89b136f82da4o%40googlegroups.com.
