bradley.meck at gmail.com
Wed Nov 2 16:07:04 UTC 2016
I assert that it cannot be seamless in JS due to the high level of
mutability. Workers seem more viable. Having workers be first class and
using something like ownership in rust might be possible, but shared
mutable heap is not safe without very fine grained and complete transfer of
ownership (this most likely would not work if things
prototypes/getters/setters survive transfer).
On Wed, Nov 2, 2016 at 11:04 AM, Leo Dutra <leodutra.br at gmail.com> wrote:
> Bradley, understood.
> And what in this algorithm would prevent it from being run in another
> thread with this same seamless code?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss