[m-dev.] thread.spawn_native

[Paul Bone]

On Tue, Jun 10, 2014 at 06:15:33PM +1000, Michael Day wrote:
>> That is, there could be separate classes of Mercury engines if
>> necessary.  A fixed number of "parallel execution workers" created at
>> startup, but also other Mercury engines created explicitly by
>> thread.spawn_native.
>
> I really like this idea. Having some control over low-level threading  
> would be very helpful. (In fairness, I don't understand the current  
> parallel execution mechanism at all).
>

If you're interested it's chapters 2 and 3 of my PhD thesis.  I'd be happy
to answer any questions.


-- 
Paul Bone