Go 1.25 Release Notes

Re:Go 1.25 Release Notes by tete on Wednesday August 13, 2025 @02:19AM (#44885182)

Yes, but with all the v2 in stdlib popping up we will get a lot of outdated code and a lot of "I need to know v1 and v2, because I will come across both".

[ Parent | on HN ]

Re:Go 1.25 Release Notes by Chiron1991 on Wednesday August 13, 2025 @03:46AM (#44885673)

But "outdated code" isn't inherently bad, is it? v1 code is still supported by the stdlib and it still does its job, at least until Go 2.x drops.

[ Parent | on HN ]

Re:Go 1.25 Release Notes by ayuhito on Wednesday August 13, 2025 @06:39AM (#44886773)

In fact, v1 code usually uses v2 code under the hood, but with different options to maintain backwards compatibility.

You still get performance improvements even if you don’t switch over to the new import!

[ Parent | on HN ]

Re:Go 1.25 Release Notes by Grokify on Wednesday August 13, 2025 @07:19AM (#44887076)

A good example is io/ioutil. It's useful to migrate to eliminate the deprecation messages, but you don't need to do it right away.

[ Parent | on HN ]

Re:Go 1.25 Release Notes by majewsky on Wednesday August 13, 2025 @07:28AM (#44887136)

Also, most of this can be automated with `go install golang.org/x/tools/gopls/internal/analysis/modernize/cmd/modernize@latest && modernize -fix ./...`

[ Parent | on HN ]