> On Sep 15, 2018, at 7:31 AM, Wojciech S. Czarnecki <o...@fairbe.org> wrote:
>
> On Sat, 15 Sep 2018 06:36:35 -0500
> Robert Engels <reng...@ix.netcom.com> wrote:
>
>> Why do you need the for...
>
> Because 'for type' means 'contract'
> Because CGG contracts are for each typeholder
> and expressed in terms of already familiar types.
>
> Thats why right after `for type` you see `T`.
>
> `for type T = constraint` "execute the body".
>
> It just reads.
>
>> Keywords with dual meaning is never a good idea.
> There always is some context to read within.
>
Not for standardized keywords like ‘for’.
Just my opinion of your proposals, the syntax is very clumsy, and not intuitive.
> See https://github.com/ohir/gonerics examples
> and point where it could be confusing.
>
> I am also open for any other contrived examples
> showing possible confusion.
>
> Note the contract placement rules as described, please.
>
> --
> Wojciech S. Czarnecki
> << ^oo^ >> OHIR-RIPE
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
