Bryan C. Mills
Bryan C. Mills
Another argument against: * A replacement may be a local or relative file path, and even if the path is relative and in the same repo, the `zip` files served...
One more against: * A user may need to supply their own `replace` directive to fix (or diagnose) an urgent issue in some module on which they depend. If their...
In some cases you can work around a slow-moving maintainer by using an actual fork (with its own import path) instead of a `replace` statement. (When the upstream is fixed,...
@josharian, ``` go list -f '{{with .Module}}{{.Path}}{{end}}' github.com/rogpeppe/go-internal/modfile ``` will give you the module containing package `github.com/rogpeppe/go-internal/modfile`.
If they're in the same root and at *compatible* versions (that is, if the code *within that submodule* hasn't changed since the requested version), I'd say leave them in the...
Completed the early-in-cycle update for the 1.15 cycle. Removing the label so we remember to revisit at the close of the cycle.
@zikaeroh, our automated scripts only pull in changes to the `golang.org/x` repos, since those are the only packages that are subject to the Go release cycle. More generally, though: if...
(CC @neild @rogpeppe @kevinburke from [CL 134395](https://go.dev/cl/134395).)
See https://go.dev/cl/416555 for a draft. 😁
> If the program was exiting due to unrecovered panic before, now it's not, and it might be in a more broken state as it keeps running. That's true, although...