The Go grammar/language changes very slowly -- most of the improvements are in the tooling and libraries, so there isn't much. But the best way is the release n

The Go grammar/language changes very slowly -- most of the improvements are in the tooling and libraries, so there isn't much. But the best way is the release notes. For the last two years (four versions): https://golang.org/doc/go1.17 https://golang.org/doc/go1.17: three very minor changes for array pointers and unsafe https://golang.org/doc/go1.16 https://golang.org/doc/go1.16: no language changes https://golang.org/doc/go1.15 https://golang.org/doc/go1.15: no language changes https://golang.org/doc/go1.14 https://golang.org/doc/go1.14: minor change to allow "overlapping interfaces" Of course, in 1.18 -- coming out in about three months -- there's the huge change to add generics (type parameters). The best way to read about that is in the type parameters proposal here: https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md https://go.googlesource.com/proposal/+/refs/heads/master/des... Go 1.18 will also add built-in fuzzing support, but again, that's a tooling/library change, not a grammar/language one.