Comment 1:

Status changed to Started.

Comment 2:

Personally I would feel that an iterator would be more convenient when reading lines.
The error could be similar to that of io.ReadFull:
"The error is EOF only if no bytes were read. If an EOF happens after reading some but
not all the bytes, ReadFull returns ErrUnexpectedEOF. On return, n == len(buf) if and
only if err == nil."
Return ErrUnexpectedEOF (or similar) if the line didn't end with a new line. Only return
EOF when no line was read.
Possibly return an error for truncated lines, ErrLineTruncated (or similar).
Line rog already pointed out: "You almost always want to strip off the final newline"
ref: https://golang.org/cl/6870052/#msg8
If a copy should be made or not is a hard choice. Can't tell at this point what my
thoughts are. It is always easy to provide a wrapper function to make the copy. The
question is, do we want to limit the need of such wrapper functions?

Comment 3:

When the line is too long (truncated) the error could be ErrPrefix to mimic the behavior
of the isPrefix bool.

Comment 4:

Re comment #3: that would be terrible. It shouldn't be possible to accidentally get a
partial line in a convenience API.  If you care about partial lines you can use the
existing bufio.Reader.

Comment 5:

This issue was closed by revision 55ad7b9.

Status changed to Fixed.