It's perfectly valid to call a method on a nil receiver, so long at the nil receiver is not dereferenced.
https://play.golang.org/p/Z-zXlj0-eVy On Wed, 2020-06-03 at 00:03 -0700, apmat...@gmail.com wrote: > Read function at net.go is like this: > > func (c *conn) Read(b []byte) (int, error) { > if !c.ok() { > > the ok checks that c is non nil: > func (c *conn) ok() bool { return c != nil && c.fd != nil } > > how can c ever be nil ? if it would c.ok() call would crash. -- 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/8b5522ffb67d8c50863f0c80582935a053be9bd1.camel%40kortschak.io.
