Go 1.6 Beta 1 is released

5,663 views
Skip to first unread message

Chris Broadfoot

unread,
Dec 17, 2015, 7:26:57 PM12/17/15
to golang-nuts
Hello Go nuts,

We have just released go1.6beta1, a beta version of Go 1.6.
It is cut from the master branch at the revision tagged go1.6beta1.

Please help us by testing your Go programs with the release, and report any problems using the issue tracker:

You can download binary and source distributions from the usual place:

To find out what has changed in Go 1.6, read the draft release notes:

Documentation for Go 1.6 is available at:

Our goal is to release the final version of Go 1.6 early February.

Cheers
Chris

Ilya Kowalewski

unread,
Dec 18, 2015, 3:08:16 AM12/18/15
to golang-nuts
Any chances of the compiler gettin faster?

DrGo

unread,
Dec 18, 2015, 4:17:48 AM12/18/15
to golang-nuts
Congratulation!

Nigel Vickers

unread,
Dec 18, 2015, 4:41:20 AM12/18/15
to golang-nuts


On Friday, 18 December 2015 09:08:16 UTC+1, Ilya Kowalewski wrote:
Any chances of the compiler gettin faster?


Would you care to be little more specific? 

like: 
this program compiled in xx secs under Go 1.5.x . It now takes xx secs under Go 1.6.x
or
my Benchmarks ran in xx secs under Go 1.5.x . They now takes xx secs under Go 1.6.x

We are seeing little or no changes between 1.5 und 1.6 in both time to Compile and the performance of the Compiled code.

In our case, time to compile is 12 to 18 % slower than 1.4.2 and this was introduced in 1.5. with the native Go compiler. The performance of the Compiled code comparison has lost relevance. Prior to 1.5 we tested for, and were experiencing ,delays relating to the GC. These delays are no longer experienced.

Nigel Vickers 

Brian Hatfield

unread,
Dec 18, 2015, 9:36:58 AM12/18/15
to Chris Broadfoot, golang-nuts
I noticed that the release notes don't make mention of https://github.com/golang/go/issues/13283, which is fixed on master (though Github doesn't seem to know about the tag go1.6beta1 in the webui - were the recent tags successfully synced to Github?).

Though I am obviously biased as the reporter of 13283, I would imagine that it's worth a note in the DNS changes block. Thoughts?

--
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Peter Kleiweg

unread,
Dec 19, 2015, 5:51:02 AM12/19/15
to golang-nuts
Why does  (*Scanner) Buffer have two arguments?

Rob Pike

unread,
Dec 19, 2015, 9:16:32 AM12/19/15
to Peter Kleiweg, golang-nuts
If you only rarely need a huge buffer, you can set max very large but start with a smaller buffer.

-rob


On Sat, Dec 19, 2015 at 2:51 AM, Peter Kleiweg <pkle...@xs4all.nl> wrote:
Why does  (*Scanner) Buffer have two arguments?

Peter Kleiweg

unread,
Dec 19, 2015, 12:24:00 PM12/19/15
to golang-nuts
I still see no fix for the godoc problem that exists since Go version 1.2. I mean where the web interface of godoc drives process load to 80 on start up, making the computer unresponsive for a few minutes.

https://github.com/golang/go/issues/6817

Is there any indication of when this will be fixed?

David Symonds

unread,
Dec 19, 2015, 3:50:27 PM12/19/15
to Peter Kleiweg, golang-nuts
That issue has a milestone of "Unplanned", so that's the indication.
It's most likely waiting for someone particularly motivated to tackle
it.

matwa...@gmail.com

unread,
Jan 1, 2016, 11:52:53 AM1/1/16
to golang-nuts
Hi all!

What about the ability to compile Go Lib to Windows DLL?

Thanks

Russ Cox

unread,
Jan 4, 2016, 8:58:36 PM1/4/16
to Brian Hatfield, Chris Broadfoot, golang-nuts
On Fri, Dec 18, 2015 at 9:35 AM, Brian Hatfield <bmhat...@gmail.com> wrote:
I noticed that the release notes don't make mention of https://github.com/golang/go/issues/13283, which is fixed on master (though Github doesn't seem to know about the tag go1.6beta1 in the webui - were the recent tags successfully synced to Github?).
Though I am obviously biased as the reporter of 13283, I would imagine that it's worth a note in the DNS changes block. Thoughts?

In general the release docs list new API and improvements of note but not bug fixes. #13283 seems like a plain bug to me, and it got fixed. Was the problem widely reported (like in blogs) or widely felt? It doesn't seem that way, but I don't have a great view of the situation. More data is always helpful.

Thanks.
Russ

Guohua Ouyang

unread,
Jan 11, 2016, 6:42:20 PM1/11/16
to golang-nuts
"It can be disabled explicitly by setting the GO15VENDOREXPERIMENT environment variable to 0.", I think there is a typo,  the variable name should be GO16VENDOREXPERIMENT.

David Symonds

unread,
Jan 11, 2016, 6:57:33 PM1/11/16
to Guohua Ouyang, golang-nuts
On 12 January 2016 at 10:42, Guohua Ouyang <guohua...@gmail.com> wrote:

> "It can be disabled explicitly by setting the GO15VENDOREXPERIMENT
> environment variable to 0.", I think there is a typo, the variable name
> should be GO16VENDOREXPERIMENT.

That's not a typo. That environment variable was introduced with Go
1.5 and controls the vendor experiment that was also introduced in
that release. Go 1.6 is only flipping the default for that experiment
to be enabled.

Guohua Ouyang

unread,
Jan 11, 2016, 7:07:26 PM1/11/16
to golang-nuts, guohua...@gmail.com
Fine, thanks. 
Reply all
Reply to author
Forward
0 new messages