On Wed, 2020-07-15 at 15:27 -0700, Bakul Shah wrote: > The second issue is the usage for generic functions. Contrast > > (float64, int)PowN(1.2, 3) > with > PowN[float64, int](1.2, 3) > or currently > PowN(float64, int)(1.2, 3) > > I find the alternate syntax easier because conceptually the concrete > types used to select a specific concrete function is a different > activity than passing arguments to a function at runtime so IMHO they > should be visually different. It is almost like C style cast. Think > of it as casting a generic function (or type) to a concrete function > or type!
This is going to be a fairly individual thing though, I find PowN[float64, int](1.2, 3) much easier to read. -- 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/d04805fe0f4341fd7542fb435c729424c4271758.camel%40kortschak.io.
