Re: Single frame continuations using yield keyword with generators compatibility proposal

> The key idea of this approach is that when a function is called that > contains a yield operator, rather than following a hard-coded > prescription to return an generator/iterator object, this triggers a > call to the startCoroutine variable (from the current lexical scope) Totally opposed. I do

Re: Single frame continuations using yield keyword with generators compatibility proposal

How does this idea compare to the Reactive Framework extensions that .NET uses? Ref: http://codebetter.com/blogs/matthew.podwysocki/archive/2009/10/14/introducing-the-reactive-framework-part-i.aspx ___ es-discuss mailing list es-discuss@mozilla.org https:

Single frame continuations using yield keyword with generators compatibility proposal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Herman's comment about JS1.7 generators spurred me to consider if we could achieve the goals stated for single-frame continuations as a broadly useful mechanism for replacing CPS code with more natural flow for constructs like promises and one-t