Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need write_file and write_lines #302

Closed
hadley opened this issue Oct 31, 2015 · 2 comments
Closed

Need write_file and write_lines #302

hadley opened this issue Oct 31, 2015 · 2 comments
Assignees
Labels

Comments

@hadley
Copy link
Member

@hadley hadley commented Oct 31, 2015

To do reverse of read_file() and read_lines() (should always write as utf-8)

@jennybc
Copy link
Member

@jennybc jennybc commented Jan 3, 2016

Could these return the path to the file they just wrote?

But I also see that would be inconsistent with write_delim() et al, which return the data frame they just wrote.

@hadley
Copy link
Member Author

@hadley hadley commented Jun 2, 2016

@jennybc I'm pretty confident now that the general principle is that if a function is called primarily for its side-effects, then it should invisibly return it's first argument.

jimhester added a commit to jimhester/readr that referenced this issue Jul 7, 2016
@jimhester jimhester added in progress and removed ready labels Jul 7, 2016
@jimhester jimhester removed the in progress label Jul 8, 2016
@lock lock bot locked and limited conversation to collaborators Sep 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants