Go 1.7.1 Released
golang.org
golang.org
net: retry DNS lookups before failure?
io: endless loop in MultiReader in Go 1.7
path/filepath: EvalSymlinks is broken for relative paths on Windows
net/http/httputil: Proxy terminates HTTP/2 stream before reading response body.
hash/crc32: wrong output for unaligned input on s390x
cmd/compile: incorrect assignment to uint64 via pointer converted to *uint16 (new in 1.7)
doc: deprecation message for Transport.CancelRequest is not correct Documentation
compress/zlib: Writer appears to ignore underlying writer errors at times.
net: NATs client can't connect to server when client built with go1.7: "dial tcp: no suitable address found"
doc: go1.7 release notes include typo for TLSConfig.NextProtos Documentation
reflect: ChanOf makes "han" types instead of "chan" types
x/mobile: Binding go mobile framework on iOS 9 with golang1.7rc6 crash when call debug.FreeOSMemory()
net/http: nil pointer dereference in closeConnIfStillIdle
website: retina favicon SuggestedWhat 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.
Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, but really doesn't belong on the front page.
I'm not sure where the line is between 'I don't find this notable' vs. 'I find this explicitly off-topic', the latter of which would warrant a flag.
Why?
Just to avoid any misunderstanding, I didn't mean to imply that Gitlab intentionally submits point releases or promotes them to the HN front page.
But even if that was the case, I don't think there is anything wrong per se with merely submitting to HN. Software releases can, and frequently are, on topic. And a point release that fixes a major security issue may certainly warrant the front page.
This is a complicated issue and every solution I can think of has significant, unacceptable unintended consequences. I also suspect this problem has deep roots in the upvoting behavior of certain kinds of users - it completely baffles me that this submission has over 60 upvotes.
Just watch my post tank now for stating this.
It's not like someone submitted it to the front page of HN? People voted it for it to come up here... and that itself should be reason enough.