Go 1.19 Beta 1 is released

[anno...@golang.org]

Hello gophers,

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

Please try your production load tests and unit tests with the new version.
Your help testing these pre-release versions is invaluable.

Report any problems using the issue tracker:
https://go.dev/issue/new

If you have Go installed already, the easiest way to try go1.19beta1
is by using the go command:
$ go install golang.org/dl/go1.19beta1@latest
$ go1.19beta1 download

You can download binary and source distributions from the Go website:
https://go.dev/dl/#go1.19beta1

To find out what has changed in Go 1.19, read the draft release notes:
https://tip.golang.org/doc/go1.19

Cheers,
Cherry, Heschi, Alex, and Dmitri for the Go team

[Amnon]

Cool!

What are the biggest, and most exciting changes coming in 1.19?

[Ian Lance Taylor]

On Sat, Jun 11, 2022 at 12:30 AM Amnon <amn...@gmail.com> wrote:
>
> What are the biggest, and most exciting changes coming in 1.19?

The draft release notes are at https://tip.golang.org/doc/go1.19 .

1.18 was a big release with a lot of exciting changes. 1.19 is more
of a relaxed, catch your breath release. Personally I think the most
exciting change is runtime/debug.SetMemoryLimit.

Ian

[ben...@gmail.com]

I'm quite looking forward to the performance improvements we'll get for free (i.e., by just upgrading): sort will be faster, large switch blocks will be faster due to now using jump tables (good for interpreter opcode-dispatch loops), and regexp will be a little faster due to a pointer-vs-value optimization (https://go-review.googlesource.com/c/go/+/355789 -- not mentioned in the Go 1.19 release notes).

-Ben

[Amnon]

debug.SetMemoryLimit will be useful (for me at least).
But a bit disappointed not to see a fix for https://github.com/golang/go/issues/50603.

[Eric Hubbard]

> debug.SetMemoryLimit will be useful (for me at least).

Me too!  :) I need to read up more about it though.  It seems to be a soft limit, not a hard limit.  We run in a container that has limited memory.. and anything we can do to make the GC aware of that limit would be nice..  

-Eric

http://www.google.com/profiles/eric.hubbard

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/bb037f28-5185-47fb-a439-23f61b7d716fn%40googlegroups.com.

[Duke]

On Friday, June 10, 2022 at 11:51:02 a.m. UTC-6 anno...@golang.org wrote:

If you have Go installed already, the easiest way to try go1.19beta1
is by using the go command:
$ go install golang.org/dl/go1.19beta1@latest
$ go1.19beta1 download

I did this on my Linux distro, but nothing happened! Where does it get DLed to?

`which go' is the old version still.

 

[ben...@gmail.com]

It doesn't replace the default "go" binary, but creates a new versioned one in the usual go-install path (~/go/bin, which a lot of folks add to their PATH). So you have to type "go1.19beta1" instead of "go":

$ which go1.19beta1

/home/duke/go/bin/go1.19beta1

$ go1.19beta1 version

go version go1.19beta1 linux/amd64

-Ben

[Duke]

Got it done! Thx ..