Comment by tapirl

Comment by tapirl 9 days ago

11 replies

View on Hacker News

Please note, currently, there are no tools to detect the new footguns created by the new semantics of 3-clause "for;;" loops: https://github.com/golang/go/issues/66156

> The second step is to keep the Go versions in our projects current. Even though we don’t use the latest and greatest language features, bumping the Go version gives us all security patches for discovered vulnerabilities.

It is not always a good strategy to use the latest toolchain version. There are often some fresh bugs in it. From the security perspective, it is better to use the previous version, which is also still being maintained.

arp242 9 days ago

Good grief, you're still banging on about this. It's been well over a year. Literally no one agrees with you. That happens sometimes. But please, accept that and give it a rest already.

Reply View 1 reply
arccy 9 days ago

you're literally the only person who's making a mountain out of a molehill coming up with ever more convoluted code to "prove" the change was a bad thing.

Reply View 5 replies
superb_dev 9 days ago

The examples in that ticket are convoluted, who would write code like that? Has this issue been spotted in the wild?

I agree that there is some issue and a lint should probably warn you about these, but I doubt a lot of people will run into it.

Reply View 1 reply