On Mon, Oct 1, 2018 at 1:53 PM, robert engels <reng...@ix.netcom.com> wrote: > > If you go to the TCPConn SetReadDeadline function, it states “implements the > Conn SetReadDeadline method”, with no way of referencing the documentation > for Conn.SetReadDeadline, in fact, no way of even getting to the Conn > interface… who knows what Conn is ??? Assume it is a Conn returned by Dial? > How do you determine this?
You're right, that is kind of useless. Would you mind filing an issue about that? It should be fixed one way or another. > Furthermore, it is not completely specified, meaning if the read timeout > occurs, and some data was read, is it discarded? will it be returned with the > next read (if any)? Doesn’t say... The behavior of the standard Read method when an error occurs is documented by the io.Reader interface. > Maybe I am looking at it wrong, but I think Go’s “simplicity” cannot be > extended to the specifications, especially when dealing with low-level > networking, api, etc. It makes it very difficult to use, and be able to > guarantee it will work the same on all platforms - hurting the portability. I'm not really sure what you're thinking of here. Ian -- 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.
