Skip to content
Prev 2498 / 12125 Next

[R-pkg-devel] Dealing with not so temporary files

Duncan gave one option. The other option is to provide a specific
write2disk() function or so that allows the user to determine whether
he/she wants to save the data. Then the user can decide exactly where he
wants to find it.

The other important part is the format in which it's saved. Users can
simply use save() or write.csv() (or any of the readr functions if you
must) to store whatever data they want in the format they want. There's a
lot of database connections possible as well if that's needed. The only
reason I see to provide a specific write function or argument, is when the
storage is done in a nonstandard format. And then it makes sense to provide
both read_myformat() and write_myformat() in some form. That's what I as an
R user would expect.

Fwiw: I have seen the commotion on that discussion recently as well, but
this is really nothing new. For as long as I remember, writing to disk only
happens when you use a function that does explicitly that. Which makes
sense as well, as eg my students often run R in a shared environment during
classes, and sysadmins don't like software that starts writing files
everywhere.

Cheers
Joris



On Tue, Mar 13, 2018 at 12:32 AM, Duncan Murdoch <murdoch.duncan at gmail.com>
wrote: