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
I am just playing with coro and it was perhaps surprising to me that when looping over an iterator with loop() and for, that the yields from the iterator are different than if I call collect(). Is this behaviour expected? Am I misunderstanding/misusing these functions? Should iterators only ever return single-element objects?
collect() returns a list with an element for each column-value for a given row, while loop()/for return the expected value which is a single row of data.
Hi @lionel-,
I am just playing with
coro
and it was perhaps surprising to me that when looping over aniterator
withloop()
andfor
, that the yields from the iterator are different than if I callcollect()
. Is this behaviour expected? Am I misunderstanding/misusing these functions? Should iterators only ever return single-element objects?collect()
returns a list with an element for each column-value for a given row, whileloop()/for
return the expected value which is a single row of data.The text was updated successfully, but these errors were encountered: