Go 1.7.1 Released
golang.org
Go 1.7.1 Released
1–10 of 30 posts
Re: Go 1.7.1 Released
#2The 14 issues tagged 1.7.1:
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 SuggestedRe: Go 1.7.1 Released
#3The 14 issues tagged 1.7.1: 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 me…
> 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?
Re: Go 1.7.1 Released
#4I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem.
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.
Re: Go 1.7.1 Released
#5The 14 issues tagged 1.7.1: 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 me…
> 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?
I think it would produce a runtime error and return a stack trace. Someone more qualified than me should chime in though...
Re: Go 1.7.1 Released
#6The 14 issues tagged 1.7.1: 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 me…
> 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?
The goroutine panics. Nil dereferences are recoverable from[1], but I'm not sure how many people expect standard library code to panic.
Re: Go 1.7.1 Released
#7I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. 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, b…
Re: Go 1.7.1 Released
#8The 14 issues tagged 1.7.1: 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 me…
> 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?
[deleted]
Re: Go 1.7.1 Released
#9I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. 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, b…
I share this sentiment. Per their own Release page [1], this one is considered a minor version with no major features, so I don't particularly find it notable, whereas a major version would probably stimulate more discussion about the new features.
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.
Re: Go 1.7.1 Released
#10I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. 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, b…
>I find it to be a problem.
Why?