> nil pointer dereference in closeConnIfStillIdle
What happens here? Does Go suffer from boundary access issues that C has? You know, in Rust, you don't have to worry about that, but is it the same for GO?
What happens here? Does Go suffer from boundary access issues that C has? You know, in Rust, you don't have to worry about that, but is it the same for GO?
package main
import "io"
func main() {
var foo io.Closer
foo.Close()
}
justin@t420:/tmp$ go run nil.go
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x20 pc=0x401023]
goroutine 1 [running]:
panic(0x463ea0, 0xc82000a140)
/usr/lib/go-1.6/src/runtime/panic.go:481 +0x3e6
main.main()
/tmp/nil.go:7 +0x23
exit status 2It has NPE (like Java or C#), though in some conditions it'll behave more like Objective-C.