Repository navigation
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2517 +/- ##
=========================================
Coverage ? 91.44%
=========================================
Files ? 63
Lines ? 12067
Branches ? 0
=========================================
Hits ? 11035
Misses ? 1032
Partials ? 0
Continue to review full report at Codecov.
|
|
Not sure about this. which would be a change from CRAN version which does this : Thoughts? |
|
Consider this file: Technically, this is not a valid CSV -- there shouldn't be a blank line there, but still, if this is the data, what do you do? You could choose a different coping strategy: (1) set Similarly, if the blank line occurs at the end, only this time fread doesn't display any warning: In both cases the CSV is still invalid, and fread deals with it in a way that it thinks is "most reasonable". Now let's go back to the case in question. Consider the following file: Unlike the first case, this is already a valid CSV: there is only one way to read it: Similarly, if the empty line occurs at the end of the file, it still remains a valid CSV file, and it should be read as such: The fact that it doesn't I view as a bug: To recap, in the first case (2+ -column file) blank lines make it an invalid CSV file, and there could be difference in opinion as to what coping strategy is best. At the same time, in the second case (1-column file) blank lines are allowed in a valid CSV file, and therefore they should be treated accordingly. |
mattdowle
left a comment
There was a problem hiding this comment.
Ok good points. I'll add a few more tests, news item and entry to manual page, and then merge.
Closes #2516