Re://go:fix inline and the source-level inliner
by avabuildsdata on Sunday March 15, 2026 @06:04PM
(#47392449)
yeah this is the part that got me excited honestly. we're not google-scale by any stretch but we have ~8 internal Go modules and deprecating old helper functions is always this awkward dance of "please update your imports" in slack for weeks. even if it doesn't let you delete the function immediately for external consumers, having the tooling nudge internal callers toward the replacement automatically is huge. way better than grep + manual PRs
[ Parent
| on HN ]
Re://go:fix inline and the source-level inliner
by shoo on Sunday March 15, 2026 @06:23PM
(#47392615)
it could be better than a nudge -- if you could get a mandatory `go fix` call into internal teams' CI pipelines that either fixes in place (perhaps risky) or fails the build if code isn't already identical to fixed code.