Y
Hacker News
new
|
ask
|
show
|
jobs
by
Chiron1991
305 days ago
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.
1 comments
ayuhito
305 days ago
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!
link
Grokify
305 days ago
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.
link
majewsky
305 days ago
Also, most of this can be automated with `go install golang.org/x/tools/gopls/internal/analysis/modernize/cmd/modernize@latest && modernize -fix ./...`
link
You still get performance improvements even if you don’t switch over to the new import!