pyalot at gmail.com
Wed Nov 2 17:32:17 UTC 2016
On Wed, Nov 2, 2016 at 6:16 PM, Bradley Meck <bradley.meck at gmail.com> wrote:
> 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.
As I've illustrated, the natural tendency of explicit tagged asynchronous
code combined with proper software engineering (separation of concerns,
modularity, reuse, interfaces, encapsulation etc.) will be to infect most
code with it, until the distinction of "explicit" becomes entirely
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss