move read.file() to fetch or keep it here or ...?

[rpruim]

We have at least 3 options:

1. Keep it here
2. Move it to fetch
3. Get rid of it altogether and have people use other tools (like readr).

I see value in each. It's not quite like the other things in fetch in that it doesn't rely on a particular back-end (Google, Gapminder, etc.) from which the fetching happens. I'm leaning toward option 1.

[nicholasjhorton]

I have never been overly enthusiastic about read.file(), since it didn't see that much simpler than just "read.csv()" or "read.table()". So I would be happy with (1) or (3).

Nick

On May 26, 2015, at 6:30 PM, Randall Pruim notifications@github.com wrote:

We have at least 3 options:

• Keep it here • Move it to fetch • Get rid of it altogether and have people use other tools (like readr). I see value in each. It's not quite like the other things in fetch in that it doesn't rely on a particular back-end (Google, Gapminder, etc.) from which the fetching happens. I'm leaning toward option 1.

— Reply to this email directly or view it on GitHub.

Nicholas Horton Professor of Statistics Department of Mathematics and Statistics, Amherst College Box 2239, 31 Quadrangle Dr Amherst, MA 01002-5000 https://www.amherst.edu/people/facstaff/nhorton

[rpruim]

Probably move this into fastR.