Good point. Without some additional rules to "freeze" it once seen in a
declaration, that would become "apples" to "oranges" very fast.
Well, I guess scratch point 3 off the list then :)
On Wednesday, June 24, 2020 at 10:55:10 PM UTC-6, haskell...@yahoo.de wrote:
>
> On Thursday, 25 June 2020 06:17:24 UTC+2, Andrey T. wrote:
>
>
>> 3. Ability to use decorated interface name as spec for type constrains
>>
>> func (type T Comparable) Max(a... T) (result T) {...}
>>
>> might become
>>
>> func Max(a... $Comparable) (result $Comparable) {...}
>>
>
> I don't see how this is equivalent. The point of the T constraint is that
> both T are the *same* Comparable type and not just any two Comparables.
>
--
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/39519adc-0af7-46b2-89e8-817b531fc183o%40googlegroups.com.
