> You already have concurrent threads of execution accessing shared mutable variables with either Promises or async/await. OS level threads are a particularly nasty variant of multitasking which I'd rather like JS to stay away from, but I don't see how that'd be an argument against co-routines.
Yes, concurrent and explicitly cooperative. I'm fine with co-routines, just explicit ones (which we currently have via generators and async functions). Implicit ones make it hard to reason about if a variable needs to place guards prior to performing any action if actions pop the stack in order to do a co-routine pause/resume. On Wed, Nov 2, 2016 at 12:11 PM, Florian Bösch <[email protected]> wrote: > On Wed, Nov 2, 2016 at 5:59 PM, Bradley Meck <[email protected]> > wrote: > >> Multiple threads are fine, but the "seamless" shared mutable variables >> are a no go on my end. >> > You already have concurrent threads of execution accessing shared mutable > variables with either Promises or async/await. OS level threads are a > particularly nasty variant of multitasking which I'd rather like JS to stay > away from, but I don't see how that'd be an argument against co-routines. > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
