]> Cypherpunks repositories - gostls13.git/commit
encoding/csv: clarify that Writer uses different line break than RFC 4180 by default
authornobishino <nobishii11@gmail.com>
Mon, 13 May 2024 21:31:18 +0000 (21:31 +0000)
committerGopher Robot <gobot@golang.org>
Mon, 13 May 2024 21:32:28 +0000 (21:32 +0000)
commit133cdfb46979064fcf359598dd2dd93ffa57cf3c
treeb5738263c697f1b837eb84f449f6b58ee924768e
parent509bbeb407f58d06a8680b48a7f02f530d67f088
encoding/csv: clarify that Writer uses different line break than RFC 4180 by default

Package documentation of encoding/csv says:

> this package supports the format described in RFC 4180.

According to section 2 of RFC 4180:

> Each record is located on a separate line, delimited by a line break (CRLF).

On the other hand, Writer uses LF (not CRLF) as newline character by default.

> If [Writer.UseCRLF] is true, the Writer ends each output line with \r\n instead of \n.

Strictly speaking, this behavior is different from RFC 4180.
Package documentation would improve if we clarify that point.

Change-Id: I120e9332b593e1ac9ed8e49f6f8419ea88efc57d
GitHub-Last-Rev: 489167eb04331fa5c623f3da9041a9d34aa258ae
GitHub-Pull-Request: golang/go#67290
Reviewed-on: https://go-review.googlesource.com/c/go/+/584835
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
src/encoding/csv/reader.go