Multiple threads are fine, but the "seamless" shared mutable variables are a no go on my end. As long as concurrent access to any existing single-thread assuming code is subject to ownership guards it seems fine. Workers, Atomics, SharedArrayBuffers, Transferables, etc. are places to look.
On Wed, Nov 2, 2016 at 11:56 AM, Leo Dutra <[email protected]> wrote: > Nop. I'm saying the opposite. > > It will be mutated and it does not matter. > Imagining that last example I gave, if "B" ran in a thread... Nothing > would change for the JS developer. "Seamless"... Magik. > > The case you are issuing is what I called a change in foundations of JS... > Making threads declared as in Java... And using volatiles. I hypothesized > about it... But the effort would be huge and I won't like to see this war. > > My proposal is break the single-thread dogma and let async, await, > promises and components run multithreaded. > > Simple, but against the a dogma. >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
