?print_linter should mention writeLines()

[MichaelChirico]

lintr/R/print_linter.R

Lines 3 to 9 in ff19b89

	#' The default print method for character vectors is appropriate for interactively inspecting objects,
	#' not for logging messages. Thus checked-in usage like `print(paste('Data has', nrow(DF), 'rows.'))`
	#' is better served by using [cat()], e.g. `cat(sprintf('Data has %d rows.\n', nrow(DF)))` (noting that
	#' using `cat()` entails supplying your own line returns, and that [glue::glue()] might be preferable
	#' to [sprintf()] for constructing templated strings). Lastly, note that [message()] differs slightly
	#' from `cat()` in that it prints to `stderr` by default, not `stdout`, but is still a good option
	#' to consider for logging purposes.

I often use writeLines() instead of cat(), e.g. replacing print() with cat() here is a bit awkward:

print(paste('time:', Sys.time()))

# ugh
cat('time: ', Sys.time(), '\n', sep='')
cat(paste('time:', Sys.time()), '\n', sep='')
# not bad in this simple example
cat(sprintf('time: %s\n', Sys.time()))

# drop-in replacement
writeLines(paste('time:', Sys.time()))