On Tue, Sep 11, 2018 at 6:56 AM <alan.f...@gmail.com> wrote:
> 2. An initialized type cannot be used directly as a method receiver, it
> must be type-aliased first:
> type FooInt = Foo(int)
> func (fi FooInt) Bar() {} // no type parameters now so clearly a
> method of FooInt
>
...
> Another problem is whether FooInt will include in its method set not just
> its own (non-generic) methods but the methods of Foo(type T) where T is an
> int. My answer to that is yes, I think it will need to do so. What do you
> guys think?
>
This is interesting, but I don't think it does exactly what you seem to
think it does.
A type alias doesn't create a new type, just a new name for an existing
type. FooInt and Foo(int) are exactly the same type, so they have exactly
the same method set. If your example were permitted, then Foo(int) would
now have a Bar() method. See https://play.golang.org/p/MrjiGvowP-j .
Although I suspect the wording in the draft doesn't actually forbid this
roundabout way of adding a method to Foo(int), after reading Ian's response
elsewhere in this thread, I'm sure he and Robert don't intend to allow it.
--
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.
