-
Notifications
You must be signed in to change notification settings - Fork 86
modfile: fix AddNewRequire block ordering #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Try to maintain the expected block ordering with direct requires in the first block and indirect requires in the second block. Also clarify expected use of SetRequireSeparateIndirect to avoid panic. Fixes #69050
This PR (HEAD: ed6e249) has been imported to Gerrit for code review. Please visit Gerrit at https://go-review.googlesource.com/c/mod/+/608056. Important tips:
|
Message from Gopher Robot: Patch Set 1: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/608056. |
Message from Steven Hartland: Patch Set 1: (2 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/608056. |
Message from Michael Matloob: Patch Set 2: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/608056. |
Message from Steven Hartland: Patch Set 2: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/608056. |
Try to maintain the expected block ordering with direct requires in the
first block and indirect requires in the second block.
Also clarify expected use of SetRequireSeparateIndirect to avoid panic.
Fixes golang/go#69050