-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/2010 11:30 AM, David Herman wrote:
function foo(...) { f-(...); g-(...); }
[snip]
Of course, and I certainly understand how continuations reify the
frame(s), and how traditional continuations preserve the stack, but I
don't follow how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/6/2010 4:04 PM, Dave Herman wrote:
function foo(...) { f-(...); g-(...); }
and the call to g throws an exception, it's perfectly easy for
an implementation to report that this came from the body of
foo.
With normal continuation passing
function foo(...) { f-(...); g-(...); }
[snip]
Of course, and I certainly understand how continuations reify the
frame(s), and how traditional continuations preserve the stack, but I
don't follow how to preserve the stack when you have broken the
continuations apart into separate autonomous
David Herman wrote:
We've given this quite a bit of time, and I don't know how far we're going to
get in understanding all the details of your proposal. But I think I can
address some of my disagreements.
1) I'm skeptical whether the requirement you stated of future-proofing code for
async
Greasing the wheels of shared-state concurrency is dangerous and
not a good idea for ES.
We definitely have not introduced shared-state concurrency
Introduced, no-- it's already there. IMO what this does is make it too easy to
trip over. You're talking about a use case where clients can
[BTW, your quoted text got garbled.]
In order to utilize leverage continuations with a function that
execute multiple we would need to eliminate single-shot restriction.
You could then create some library function that passed the
continuation to the setInterval function to do something like:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/5/2010 10:26 AM, David Herman wrote:
[BTW, your quoted text got garbled.]
In order to utilize leverage continuations with a function that
execute multiple we would need to eliminate single-shot
restriction. You could then create some
David Herman wrote:
Your answers keep leaving out the definition of the function that you're calling
via `-', which is supposed to be the part that creates the requisite object
with `continueWith' etc. Examples don't do much good if they skip the part they
were supposed to illustrate!
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/2010 9:45 AM, Dave Herman wrote:
I am not exactly sure what that intent is here, but I am guessing it
is supposed to flash several times before showing the alert.
No, sorry that I meant window.setInterval rather than
window.setTimeout,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/2010 10:56 AM, David Herman wrote:
Hi Kris,
I've been poring over this for a while, and it's still really,
really confusing. Could I ask you to show how you would write the
following example with your proposal?
function setup() {
I am not exactly sure what that intent is here, but I am guessing it
is supposed to flash several times before showing the alert.
No, sorry that I meant window.setInterval rather than window.setTimeout, but
otherwise I think I wrote what I meant. I wanted it to alert done setup!
immediately
Hi Kris,
I've been poring over this for a while, and it's still really, really
confusing. Could I ask you to show how you would write the following example
with your proposal?
function setup() {
setFlashing(document.getElementById(notificationArea));
alert(done setup!);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wanted to propose the addition of a new syntax and API for
single-frame continuations in ES6. The use of callback functions to
continue the execution of code is extremely common pattern in
JavaScript, particularly with asynchronous operations where
Kris,
Thanks for this proposal. I think it's got a lot going for it. I like the
simplicity of the API, although I think it could be simplified even further.
This is often called continuation passing style (CPS) and is
quite verbose in JavaScript, difficult to debug, and can be very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/30/2010 4:20 PM, David Herman wrote:
Kris,
Thanks for this proposal. I think it's got a lot going for it. I
like the simplicity of the API, although I think it could be
simplified even further.
This is often called continuation passing
15 matches
Mail list logo
