/cc @griesemer

This seems like a job for goimports, since gofmt has never split import groups yet goimports does so by design.

If you have a bunch of related renamings then you may want to see them all together. If you have just a few in a large list of imports, the benefit of sorting them with the normal imports is that when you look for a particular import you only need to consider one list. For example in cmd/go we have variables named 'path' quite a bit, so conventionally the import of "path" comes in as pathpkg. Here's one real import block:

import (
	"bytes"
	"fmt"
	"go/build"
	"go/token"
	"io/ioutil"
	"os"
	pathpkg "path"
	"path/filepath"
	"sort"
	"strconv"
	"strings"
	"unicode"
	"unicode/utf8"

	"cmd/go/internal/base"
	"cmd/go/internal/cfg"
	"cmd/go/internal/modinfo"
	"cmd/go/internal/search"
	"cmd/go/internal/str"
)

I think it would be inappropriate for gofmt or goimports to force moving the path import into its own section.

We intentionally leave this to local custom - gofmt and goimports will never move imports across blank lines in the import block. So if I want path with the others, I can do that, and gofmt/goimports respect that. And if you want all your renamed imports together, you can do that, and gofmt/goimports respect that too.

There's not a compelling reason to force everyone onto one side or the other.