Skip Breidbach
06/04/2020, 11:23 PMLOOP
construct. The scenario I have in mind is that I have one task that is generating a series of chunks of data. Each chunk would ideally start to be processed by a different downstream task before the generator task completes. I don't know how many it will create in advance, so I don't think I can map
the task. (It's also possible that I'm just thinking about the problem the wrong way.)Chris White
06/05/2020, 1:15 AMSkip Breidbach
06/05/2020, 4:03 PMLOOP
construct also creates child tasks. Would those child tasks also work with depth-first-execution? (Or does the entire LOOP
need to complete before any dependent tasks could begin?)Chris White
06/05/2020, 4:20 PMSkip Breidbach
06/05/2020, 4:21 PMHawkar Mahmod
08/28/2020, 1:46 PMLOOP
construct. But I would like to be able to return the value of particular iteration to downstream tasks for processing and then combine the result.Skip Breidbach
08/28/2020, 5:41 PMLOOP
result is an atomic unit. That example appears to show executing one Task
that internally uses LOOP
multiple times (potentially in parallel) via map
. But I don't think it's letting you see the result of a specific LOOP
iteration, only the final result.