But, given that this one should be used inside an optimized block, are you sure that users will call aggregate and friends only with parallel-friendly operations? Ensuring that only a sequential computation is maybe better, we don't want to force parallelism on the user if he didn't request it.

Also, not spawning helper tasks to potentially help completing the operation means that the minimum size where this optimization is viable should become smaller.

DarkDimius <notifications@github.com> wrote:
>> @@ -180,6 +199,22 @@ object Scheduler {
>>      }
>>    }
>>  
>> +  object Dummy extends WorkstealingTree {
>
>I dont want to ommit creating a WorkStealingTree, as I want to live
>possibility for 'helpers' coming to help with computation in future.
>I've fixed minimum size for equilibrium, see comment above.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/scala-blitz/scala-blitz/pull/14/files#r7880932

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.