Can go:linkname enable zero‑downtime upgrade of a small Go app across releases?
Background When migrating a lightweight Go service, the goal is to replace the running binary without service interruption. A common strategy is to launch the new process, allow it to accept traffic, then shut down the old instance. The go:linkname compiler directive can expose unexported functions or variables from a dependency, potentially allowing the new
go