Comment 1:

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

Owner changed to @griesemer.

Status changed to Accepted.

Comment 2:

The previous issue about this was issue #680. We decided that \r is ignored so that \r\n
becomes \n in multiline `` literals. So this seems like just an update to go/scanner to
do the same in comments.

Comment 3:

Note: go/scanner is doing the right thing and stripping the CRs in comments,
scanner_test.go tests for it. The CR must be sneaking in elsewhere, possibly via
go/printer.

Comment 4:

Labels changed: added go1.1.

Comment 5:

I cannot reproduce this: Try e.g.: http://play.golang.org/p/qNfUiJ5lGf which takes your
example, introduces the \r\n's and then invokes gofmt on it. The \r\n's are gone
afterwards.
(You need to copy playground source into a local file, say test.go, and run it with: "go
run test.go" because the gofmt executable is not available in the playground. Make sure
gofmt is in your $PATH).
Similarly, when storing the source as a file with \r\n line endings (crlf.go) and
applying both gofmt or go fmt, the \r\n's are gone and replaced by \n's everywhere.
Finally, go/scanner is testing explicitly that the \r's are gone.
Perhaps your favorite editor is doing something funny? I am going to close this. If you
have a concrete test case that misbehaves (executable source - no manual steps that rely
on some 3rd party editor), than you can reopen this. Thanks.

Status changed to WorkingAsIntended.

Comment 6:

I can reproduce this. Will show gri offline.

Status changed to Accepted.

Comment 7:

This is broken in go1.0.x but fixed at tip. It will be fixed in the
go1.1 release.

Status changed to Fixed.