> new slice to array conversions

I expect this to bite a few people in places they didn't know could hurt. Better grep your code for slice-to-array conversion.

Note that afaik [3]string(s) was not valid before go1.20 so no existing code should use it. The semantic equivalent had to be written as *(*[3]string)(s) which also copies the array pointed to by *[3]string)(s). The new notation is basically a shorthand and easier to discover than using *(*[3]string)(s): https://github.com/golang/go/issues/46505

Right. It was not a well-formed conversion. My bad.

Also particular note from the linked general release notes:

> Go 1.20 is the last release that will run on any release of Windows 7, 8, Server 2008 and Server 2012. Go 1.21 will require at least Windows 10 or Server 2016.

Windows 7 Extended Security Updates ending today expect to see that across a lot of software.

Title isn't great because this is just one part about the language changes, not standard library changes.

Is it just me or go looks like more and more brainfuck language after each new version?