cmd/go/internal/modfile: add new requires to end of file

The old behavior was to add new requires to the first require statement in the file.

If there's more than one statement, though, it's more convenient for the first N-1
to be the manually maintained ones and then have the (possibly large) auto-maintained
block at the end of the file, instead of putting the manually maintained statements
after a giant auto-maintained one.

Suggested by Bryan Mills in an earlier CL, and works better for some real use cases.

Change-Id: I17a1704ca459c8cb5536dc23997bbacc3cd997eb
Reviewed-on: https://go-review.googlesource.com/121859
Reviewed-by: Bryan C. Mills <bcmills@google.com>
2 files changed
tree: 0e05a870571e0b5cd58cd290fc1e0837db8fcd72
  1. AUTHORS
  2. CONTRIBUTING.md
  3. CONTRIBUTORS
  4. LICENSE
  5. PATENTS
  6. README.md
  7. codereview.cfg
  8. main.go
  9. vendor/
README.md

Versioned Go Prototype (vgo)

This repository holds a prototype of what the go command might look like with integrated support for package versioning.

See research.swtch.com/vgo for documents about the design.

Download/Install

Use go get -u golang.org/x/vgo.

You can also manually git clone the repository to $GOPATH/src/golang.org/x/vgo.

Report Issues / Send Patches

See CONTRIBUTING.md.

This is still a very early prototype. You are likely to run into bugs. Please file bugs in the main Go issue tracker, golang.org/issue, and put the prefix x/vgo: in the issue title.

Thank you.