Note: this is not an implementation issue, this is a shared access introducing bugs issue.
On Wed, Nov 2, 2016 at 10:10 AM, Leo Dutra <[email protected]> wrote: > Bradley, JIT can take care of it. If too hard... "volatile" reserved word > is around since the early 00's. > > > > *Leo Dutra, **on **Facebook <http://www.facebook.com/leodutra.br> **and > LinkedIn > <https://www.linkedin.com/in/leobr>* > > 2016-11-02 13:03 GMT-02:00 Bradley Meck <[email protected]>: > >> >> > As I said... JS has mutable objects by default. The memory space SHALL >> be the same. >> >> > What is not being covered? Let it come to the surface. >> >> As stated, that single threaded access to objects and shared memory >> multi-threaded access are very different. >> >> On Wed, Nov 2, 2016 at 9:56 AM, Leo Dutra <[email protected]> wrote: >> >>> Message passing between two objects is a Law of Nature, broad and >>> powerful. >>> But there's more than just workers and process spawn in life. >>> >>> As I said... JS has mutable objects by default. The memory space SHALL >>> be the same. >>> >>> Atomic could handle the racing when needed and a Mutex for locking. >>> >>> What is not being covered? Let it come to the surface. >>> >> >> >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
