Yes. There's also the unfortunate collision with io.ReaderFrom's method
name which is directionally opposite to net.PacketConn's ReadFrom. This
is unfixable because of Go1.
Dan
On Mon, 2019-05-13 at 15:14 -0700, Ian Lance Taylor wrote:
> On Mon, May 13, 2019 at 2:45 PM Dan Kortschak
> wrote:
>
On Mon, May 13, 2019 at 2:45 PM Dan Kortschak wrote:
>
> Thanks, Jake. This was very helpful.
It does seem that the docs in this area should be improved. Alas.
Ian
> On Mon, 2019-05-13 at 09:19 -0700, jake6...@gmail.com wrote:
> > On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak
Thanks, Jake. This was very helpful.
On Mon, 2019-05-13 at 09:19 -0700, jake6...@gmail.com wrote:
> On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak wrote:
> >
> >
> > The Conn and UDPConn Read methods look like io.Reader Read methods,
> > butÂ
> > there is no explicit claim that Conn is
On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak wrote:
>
> The Conn and UDPConn Read methods look like io.Reader Read methods, but
> there is no explicit claim that Conn is an io.Reader. Are the Read
> methods of these two types identical in behaviour to io.Reader?
>
I can not say
