Update man/fwrite.Rd

ben-schwen · MichaelChirico · web-flow · commit eb17a3464b25 · 2025-08-05T16:43:15.000+02:00
Co-authored-by: Michael Chirico &lt;chiricom@google.com&gt;
diff --git a/man/fwrite.Rd b/man/fwrite.Rd
@@ -63,7 +63,7 @@ fwrite(x, file = "", append = FALSE, quote = "auto",
   \item{bom}{If \code{TRUE} a BOM (Byte Order Mark) sequence (EF BB BF) is added at the beginning of the file; format 'UTF-8 with BOM'.}
   \item{verbose}{Be chatty and report timings?}
   \item{encoding}{ The encoding of the strings written to the CSV file. Default is \code{""}, which means writing raw bytes without considering the encoding. Other possible options are \code{"UTF-8"} and \code{"native"}. }
-  \item{forceDecimal}{ Should decimal points be forced for whole numbers in numeric columns? When \code{TRUE}, whole numbers like \code{c(1.0, 2.0, 3.0)} will be written as \code{1., 2., 3.} instead of \code{1, 2, 3}. Default is \code{FALSE}. }
+  \item{forceDecimal}{ Should decimal points be forced for whole numbers in numeric columns? When \code{FALSE}, the default, whole numbers like \code{c(1.0, 2.0, 3.0)} will be written as \samp{1, 2, 3} i.e., dropping \code{dec}. }
 }
 \details{
 \code{fwrite} began as a community contribution with \href{https://github.com/Rdatatable/data.table/pull/1613}{pull request #1613} by Otto Seiskari. This gave Matt Dowle the impetus to specialize the numeric formatting and to parallelize: \url{https://h2o.ai/blog/2016/fast-csv-writing-for-r/}. Final items were tracked in \href{https://github.com/Rdatatable/data.table/issues/1664}{issue #1664} such as automatic quoting, \code{bit64::integer64} support, decimal/scientific formatting exactly matching \code{write.csv} between 2.225074e-308 and 1.797693e+308 to 15 significant figures, \code{row.names}, dates (between 0000-03-01 and 9999-12-31), times and \code{sep2} for \code{list} columns where each cell can itself be a vector.

Original file line number	Diff line number	Diff line change
`@@ -63,7 +63,7 @@ fwrite(x, file = "", append = FALSE, quote = "auto",`
`63`	`63`	`\item{bom}{If \code{TRUE} a BOM (Byte Order Mark) sequence (EF BB BF) is added at the beginning of the file; format 'UTF-8 with BOM'.}`
`64`	`64`	`\item{verbose}{Be chatty and report timings?}`
`65`	`65`	`\item{encoding}{ The encoding of the strings written to the CSV file. Default is \code{""}, which means writing raw bytes without considering the encoding. Other possible options are \code{"UTF-8"} and \code{"native"}. }`
`66`		`- \item{forceDecimal}{ Should decimal points be forced for whole numbers in numeric columns? When \code{TRUE}, whole numbers like \code{c(1.0, 2.0, 3.0)} will be written as \code{1., 2., 3.} instead of \code{1, 2, 3}. Default is \code{FALSE}. }`
	`66`	`+ \item{forceDecimal}{ Should decimal points be forced for whole numbers in numeric columns? When \code{FALSE}, the default, whole numbers like \code{c(1.0, 2.0, 3.0)} will be written as \samp{1, 2, 3} i.e., dropping \code{dec}. }`
`67`	`67`	`}`
`68`	`68`	`\details{`
`69`	`69`	\code{fwrite} began as a community contribution with \href{https://github.com/Rdatatable/data.table/pull/1613}{pull request #1613} by Otto Seiskari. This gave Matt Dowle the impetus to specialize the numeric formatting and to parallelize: \url{https://h2o.ai/blog/2016/fast-csv-writing-for-r/}. Final items were tracked in \href{https://github.com/Rdatatable/data.table/issues/1664}{issue #1664} such as automatic quoting, \code{bit64::integer64} support, decimal/scientific formatting exactly matching \code{write.csv} between 2.225074e-308 and 1.797693e+308 to 15 significant figures, \code{row.names}, dates (between 0000-03-01 and 9999-12-31), times and \code{sep2} for \code{list} columns where each cell can itself be a vector.