I'm writing a library in Go that I'm compiling to a native library using CGo, however when the functions are exported they have this annoying empty line between the function declaration and the documentation comment.

As an example, let's say I have this in my go file

/**
 * Prints an integer.
 *
 * @param p0 an integer to print.
 */
//export PrintInteger
func PrintInteger(val C.int) {
    fmt.Printf("%v", val);
}

Once it's exported in my C header file, it looks like this

/**
 * Prints an integer.
 *
 * @param p0 an integer to print.
 */

extern void PrintInteger(int p0);

That empty line for the most part isn't a problem, but on some IDEs when parsing that header file they have difficulty properly displaying the intellisense, making consumption of the header slightly more difficult. Especially when you factor in the way that cgo renames function parameters

I've found what i believe is the area in the go source code that causes this:

https://github.com/golang/go/blob/master/src/cmd/cgo/out.go#L922

if len(exp.Doc) > 0 {
    fmt.Fprintf(fgcch, "\n%s", exp.Doc)
}
fmt.Fprintf(fgcch, "\nextern %s;\n", s)

I feel like perhaps that \n before the extern keyword shouldn't be there. Unless this is intentional?