Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: document best practice for “postdated” requirements #26150
I want to express a dependency on an unreleased upstream fix.
I think the right way to do that is to
I'd like to confirm that or find a better alternative.
(This issue is motivated by thinking about some edge cases in https://golang.org/cl/121000.)
Suppose that own module
I discover a bug in
Now I want to advertise the fix so that my users will test against it. My users (and their users, and so on) will have to add their own
I want my pre-release to fail to build before
That suggests that my
Is that the best way to address my use-case?