Comment 1:

Labels changed: added priority-later, removed priority-triage.

Comment 2:

IIUC, "// foo" remains attached to the function just because is treated as a godoc
comment. The convention is that comments precede the function definition, so I would not
call the current behavior "incorrect".
Since in this use case it is not really a godoc comment, I'd suggest considering a
different convention for go present that does not interfere with the pre-existing godoc
one. (E.g. "// START" and "// STOP" surrounded by blank lines.) Alternatively, if godoc
is never to be used with go present source files, having different gofmt modes might be
an option as well (distinguished via a command line option or some marker in the source).
If the gofmt behavior is to be changed universally, it should be designed such that both
of these are handled correctly, which does not seem straightforward to me:
// START
func f() {
}
// END
// START
func g() {
}
// END
...
// Function f blahblahblah...
// blahblahblah...
func f() {
}
// Function g blahblahblah...
// blahblahblah...
func g() {
}
...
Just my two cents.

Comment 3:

I don't think it's worth bothering with 
// start
func f() {}
// end
either, but if we do we would certainly have to disable the logic for
// start
func f() {}
// end
func g() {}
Thanks for the reminder.

Comment 4:

Labels changed: added size-m.

Comment 5:

Go 1.1 is too close. Postponing.

Labels changed: added go1.2, removed go1.1.

Comment 6:

Labels changed: added go1.3, removed go1.2.

Comment 7:

Labels changed: added release-go1.3.

Comment 8:

Labels changed: removed go1.3.

Comment 9:

Labels changed: added repo-main.

Comment 10:

Changing the behavior for comments following a declaration will indeed require
significantly more logic to do the "right thing". Leaving this one alone.

Status changed to WorkingAsIntended.