Le 21/04/2013 19:09, Brendan Eich a écrit :
Domenic Denicola wrote:
Doing a quick poll of some IRC rooms, there's some call for shared-memory multithreading. I know this was a concern of the asm.js project, or more generally for the JS-as-a-compilation-target mission. I don't think this is a good idea, but just passing it along.

We're researching still and will not let arbitrary data races violate JS semantics (for one thing, this would hit all JITs that speculate assuming invariants obtained from JS's event-loop concurrency within the same realm, er, window -- it would break them all, AFAICT).

It may be that a Parallel JS "patient parent" model where non-overlapping slices of an array-buffer are handed off to workers, with results written back race-free, is enough for the interesting use-cases.
Data ownership (like HTML5 Transferables or Rust unique pointers) is another interesting track that covers different (also interesting) use cases in my opinion. Probably to be considered as part of the ES7/ES8 work on "The semantics of inter-vat communications"

David
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to