Better would be a got vet check.

I understand the need not to break existing code that might have such fields.

I think that's a no-go because vet checks have no-false-positive policy. Ie, when go vet flags something, its a bug.

I would say that initialising the wrong field because a dev is unaware of a clash between Gopher.Burrow and Gopher.Habitat.Burrow (naturally in more complex code), when upgrading to 1.27 and taking advantage of the feature without realising it, is a bug.

Well either way, these things usually land in golangci-lint first and get promoted if they're deemed useful enough.