Michael Matloob
Michael Matloob
I tried running make.bash at `6d93de2c110f66457f103c33ba496ff2e2bf33af` using a Go 1.22.4 bootstrap toolchain and wasn't able to reproduce. It seems like we should close this and reopen if you see the...
Okay, created backport issues https://github.com/golang/go/issues/68221 and https://github.com/golang/go/issues/68222
I don't recall any changes specifically to openbsd
I just had a chance to look into this. On the `pomerium@f54b1a7d098fac76c7ddbccdb9351483466b7b6a` example the behavior is as expected (though perhaps we should change the expectation). The third require block has...
I think this issue gives some support that we should do something. I think we have evidence that it's easy to get into a confusing state (having a requirement marked...
@thediveo The design we have was intended: we wanted to allow users to be able to define their own sections that we'd leave alone. So we only modify the all-direct...
This seems reasonable to me. Thanks for the CL!
I'm not opposed to this. I think it would require going through the proposal process because it's an API change to the standard library
@hdonnay do you want to turn this into a proposal issue?
I think that since we support `go run pkg@version` it makes sense to also support `go build pkg@version` like others have suggested. Though I wonder if we might want to...