The command line go doc command rocks. I think the new GC and changes allowing GOMAXPROCS  to use more cores by default are a great milestone.

Thanks Go Team.

>But isn't one month of beta testing not enough?

They actually entered a code freeze a while ago, and I think many people test with the git version as it comes along.

Hi guys,

https://github.com/bradfitz/http2 won't be add in this release? Or I missed something?

I am using windows 64 version and when i compile my code i get following error:

Cross compilation is not slower than native compilation.

However, the compiler is, unfortunately, somewhat slower in 1.5.  We
are going to work hard to speed it up in 1.6.  But 1.5 is not, in our
measurements, 10 times slower--it's not even twice as slow for most
builds.  I don't know why you are seeing such a slowdown.  You may be
hitting a particularly bad case for some reason.  I would encourage
you to investigate what specifically is slow, and open an issue if you
find anything interesting.

Ian

From what I've heard, HTTP/2 will hopefully be included in Go 1.6.

Now for some good news...

In my project (a compiler/interpreter/vm) which uses lots and lots of
interfaces and generates astounding amounts of garbage, when I compile
it with go 1.5 beta it runs 20-25% faster than go 1.4.

I can see the CPU usage going above 100% in this single threaded program
which means the concurrent garbage collector is working well.

Well done the Go team!

--
Nick Craig-Wood <ni...@craig-wood.com> -- http://www.craig-wood.com/nick

Also, there is a 1.5beta1 tag for the library/golang docker image as well.  

Hello, and great job!

We have an http test that passes with go1.4 but fails with go1.5beta1.

Our http handler has an explicit check against content length too long:

       if r.ContentLength >= contentLengthLimit {
                w.WriteHeader(http.StatusBadRequest)
                return
        }

Our tests check for the 400 code back, but now the test returns an error instead getting a response back:

        req, _ := http.NewRequest(method, url, strings.NewReader(contents))
        client := &http.Client{}
        resp, err := client.Do(req)
        if err != nil {
                t.Fatal(err)
        }

In go1.4 client.Do() would return with err==nil, but in go1.5beta1 the error comes back "Put http://localhost:8080/debug/test_program.json: write tcp 127.0.0.1:53000->127.0.0.1:8080: write: connection reset by peer"

This appears to be the intended behavior after https://github.com/golang/go/commit/1045351cef21a64d954b4477af9f5105ea4287d3

I don't necessarily think this is a regression, but still might be worth mentioning in the release notes.

Thanks,
Tarmigan

Can you file a bug with more details for me to track?

I agree that the correct response is not obvious in this case.  Ticket is http://golang.org/issue/11745