Thread by @mvdan_

Here's a short list of the changes to look forward to for #golang 1.17, to start landing once the merge window opens in a few weeks.

Don't get confused with 1.16, releasing next month. 1.17 will come out in seven months.

Each change with a link, so you can read more.

A register-based calling convention for Go functions. Backwards compatible, and should give 5-10% speed improvements across a range of applications.

github.com/golang/go/issu…

First class fuzzing support in the Go toolchain. This work has been happening behind the scenes in the dev.fuzz branch for some months, so I hope it will start landing for 1.17.

golang.org/s/draft-fuzzin…

Lazy module loading, which should especially help when developing large projects with deep module dependency graphs.

github.com/golang/go/issu…

Allowing replacement modules to alias other active modules. Useful when working with temporary forks.

github.com/golang/go/issu…

A language change! (*[4]int)(x) to get a slice's underlying array pointer, without the use of unsafe.

A small addition, but it opens interesting possibilities.

github.com/golang/go/issu…

Bonus round 1: The register-based ABI work is happening in the dev.regabi branch. It also includes large compiler refactors, which are enabling changes to make the compiler smarter in other areas.

go-review.googlesource.com/q/project:go+b…

Bonus round 2: The dev.typeparams branch continues to advance, implementing the latest generics proposal. Beware that it's not expected to start landing until Go 1.18, though.

go-review.googlesource.com/q/project:go+b…