4 ms·
Go 1.20
- deleted 4y ago[deleted]
- tgv 4y ago> 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.
- martisch 4y agoNote 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 https://github.com/golang/go/issues/46505
- tgv 4y agoRight. It was not a well-formed conversion. My bad.
- zamadatix 4y agoAlso 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.
- earthboundkid 4y agoTitle isn't great because this is just one part about the language changes, not standard library changes.
- greatgib 4y agoIs it just me or go looks like more and more brainfuck language after each new version?
- dopp0 4y agoI feel the same... GoLang as a platform looks perfect, but syntax-wise it could be much simpler. I'm not sure why it is not, I think they try to differentiate from other languages, that's the only reason. Looks like C++ on steroids.