On Wednesday, June 17, 2020 at 5:50:24 PM UTC-7, Ian Lance Taylor wrote: > > On Wed, Jun 17, 2020 at 9:36 AM Charles Crete <cha...@cretezy.com > <javascript:>> wrote: > > > > Based on the new proposal, having the type parameters as () seems very > confusing, as now 3 things in a row use (): > > - Type parameters > > - Function parameters/arguments > > - Return tuple > [cut] > > Let's try the current suggested syntax and see how it works out in > practice. > > > https://go.googlesource.com/proposal/+/refs/heads/master/design/go2draft-type-parameters.md#why-not-use-the-syntax-like-c_and-java > > > Ian >
I agree with others that multiple () blocks on the same line is hard to read (so far, at least). In general, I think parser complexity should come second to the cognitive complexity of humans reading code. Any other means of separating type parameters in a more visually distinctive way would seem preferable. Regards, -Sam. -- 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/7a576cef-cca5-433c-ae79-196b895212d5o%40googlegroups.com.
