On Sat, Jun 4, 2016 at 12:07 PM, Ben Coman btc@openinworld.com wrote:
So having *mostly* produced a technical proof of concept (for StackVM), the meta-question is whether a change like this worth pursuing? Apart from my own need for the OwnedLock primitiveWaitAcquire, I have cluelessly wondered if there might be any benefit for multi-threading or callback patterns, now or in the future.
Also, are there any obvious/known difficulties to be expected doing this with JIT side?
I'll hold back from those questions for now. I'm trying an alternative approach that doesn't involve changing the cross-suspension primitiveFail semantics.
cheers -ben
vm-dev@lists.squeakfoundation.org