@bradfitz @josharian

This seems arbitrary either way, no? It chose something, so that should be fine, just like the rest of the spirit of gofmt?

Help message said "put imports beginning with this string after 3rd-party packages; comma-separated list" though. Also if the import block is

import (
        "fmt"
        "github.com/cespare/wait"
)

, then goimports will change it to

import (
	"fmt"

	"github.com/cespare/wait"

	"liftoff/go/timeutil"
)

Okay, if it contradicts the docs, that might be reason enough to change it.

I don't object if you send a CL. Others might argue it's better to fix the docs, but I'll let them make that case if so.

We're seeing this as well. Our CI catches badly formatted imports and they've been failing recently, even though everyone has setup filewatchers in Goland with the -local option. goimports used to do what the docs mentioned (i.e., putting local packages last), so this is a regression.

Specifically, goimports does not reorganize the below:

import (
    "net/http"
    "strings"

    "github.com/local/repo/pkg/test"

    "github.com/pkg/errors"

    "github.com/local/repo/bar"
    "github.com/local/repo/foo"
)

@af-engineering for Goland you can fix that by using goland settings https://youtrack.jetbrains.com/issue/GO-7321

Looked into this a bit since I tripped over this as well. The fundamental issue here seems to be that goimports doesn't reorder existing imports across empty lines (only if there are e.g. external and local imports in the same "group", additional empty lines are inserted). This is also explicitly tested against in TestSimpleCases/new_section_for_all_kinds_of_imports. IMO just always reordering into three groups (stdlib, external and local), disregarding existing separation lines, would be clearer. Would that be an acceptable change or is this too opinionated?