Breaks import comment

[AlexanderYastrebov]

I've noticed this while playing with formatting go sources

gofumpt -d ./net/dnsclient.go

diff ./net/dnsclient.go.orig ./net/dnsclient.go
--- ./net/dnsclient.go.orig
+++ ./net/dnsclient.go
@@ -5,15 +5,19 @@
 package net
 
 import (
+       "sort"
+       _ "unsafe"
+
        "internal/bytealg"
        "internal/itoa"
-       "sort"
-       _ "unsafe" // for go:linkname
+
+       // for go:linkname
 
        "golang.org/x/net/dns/dnsmessage"
 )
 
 // provided by runtime
+//
 //go:linkname runtime_rand runtime.rand
 func runtime_rand() uint64

[mvdan]

Yep, for better or worse, this is how comments in Go work at the moment. Reordering or moving imports is also a bit broken right now, e.g. see #225. The handling of import declarations needs a bit of a rethink.

[boris-smidt-klarrio]

Another case i noticed is when the comment is above the import it doesn't get moved either.

 import (
// import for x, y z reason
"hello"
)

[sitano]

this also breaks other linters that use #nolint there