What’s New in Go 1.20, Part I: Language Changes

Re:What’s New in Go 1.20, Part I: Language Changes by tgv on Tuesday January 10, 2023 @08:35AM (#34324618)

> 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.

[ Parent | on HN ]

Re:What’s New in Go 1.20, Part I: Language Changes by martisch on Tuesday January 10, 2023 @08:49AM (#34324786)

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

[ Parent | on HN ]

Re:What’s New in Go 1.20, Part I: Language Changes by tgv on Tuesday January 10, 2023 @08:59AM (#34324894)

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

[ Parent | on HN ]