On Jul 14, 2020, at 5:54 PM, 'Robert Griesemer' via golang-nuts
<golang-nuts@googlegroups.com> wrote:
>
> But if we are comfortable with the extra type keyword, the ambiguity
> disappears:
>
> type A[type N] E
>
> (When we originally dismissed square brackets, the type keyword was not yet
> on the table.)
>
> Furthermore, the ambiguities that arise with parentheses appear not to arise
> with square brackets. Here are some examples where extra parentheses are not
> needed with square brackets:
>
> using () using []
> func f((T(int)) func f(T[int])
> struct{ (T(int)) } struct{ T[int] }
> interface{ (T(int)) } interface{ T[int] }
> [](T(int)){} []T[int]{}
Just my $0.02: I really like this. Thank you for responding to feedback, and I
look forward to trying the new syntax out!
- Dave
--
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/6C145CFD-7A43-4BAA-87AA-5E3AA00C068C%40gmail.com.
