You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have quite strange rbind() behavior when the argument type is an iterator. For example, when we have a test.csv file with the following content
c1, c2, c3
1, 2, 3
read it with iread() multiple times and want to rbind the results, a typical use-case for iread(), this is what happens
Currently we have quite strange
rbind()
behavior when the argument type is an iterator. For example, when we have atest.csv
file with the following contentread it with
iread()
multiple times and want to rbind the results, a typical use-case foriread()
, this is what happensThe error message is not very helpful. In some cases (cannot reproduce it now) the message even looks like this
We should either support frame iterators directly in
rbind()
(the preferred way), or explicitly say they're not supported.The text was updated successfully, but these errors were encountered: