Fixed. What it's doing now is wrap the input enumerable into a caching enumerable and then feed a clone of each row into the operations making up the branch.
On Thu, Jul 2, 2009 at 16:53, webpaul <[email protected]> wrote: > > Looking at the code, I think the only reason it isn't yield returning > right now is so it can copy the rows. If you make an IEnumerable that > copies the rows one at a time and feed that to the operation.Execute I > think that is all that is needed. > > On Jul 2, 7:17 am, zvolkov <[email protected]> wrote: > > uhh... maybe cache only a few rows but not all? Assuming I branch in > > 2, at worst I will need to cache as many rows as there is the > > disparity between the two consumers of my two output streams... Makes > > sense? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
