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

Confusing behaviour for CSV #133

Closed
christophergandrud opened this issue Nov 30, 2016 · 2 comments
Closed

Confusing behaviour for CSV #133

christophergandrud opened this issue Nov 30, 2016 · 2 comments
Labels
Milestone

Comments

@christophergandrud
Copy link
Contributor

The documentation seems to imply that when a file has a .csv extension read.csv is used by default and that fread is only used if fread = TRUE. However, fread = TRUE appears to be the default behaviour.

When fread = FALSE it doesn't appear that read.csv is actually used. Here is an example:

screen shot 2016-11-30 at 11 01 32

Sorry, I'm in a hurry and haven't had time to figure out what procedure is being used here, but this is the same data with read.csv:

screen shot 2016-11-30 at 11 02 49

Note: I'm using version 0.4.16

@leeper leeper added the bug label Nov 30, 2016
@leeper leeper closed this as completed in a634fff Dec 5, 2016
@leeper
Copy link
Contributor

leeper commented Dec 5, 2016

Thanks. This should now be fixed.

@leeper leeper added this to the v0.5 milestone Dec 5, 2016
@christophergandrud
Copy link
Contributor Author

Great. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants