3 ms·
It's not the continuations which are the problem, it's relying on state at all. As the submission describes, storing the state used too much RAM and required pr
by andreasvc 12y ago
It's not the continuations which are the problem, it's relying on state at all. As the submission describes, storing the state used too much RAM and required pruning. The solution was to reformulate the problem so as not to require state, if possible.
- brudgers 12y agoI don't claim expertise, but my understanding is that it is considered difficult to compute without states because the critical question is, "What is the next state?" Continuations are a way of answering that question asynchronously in regard to the timing of the invocation of the transition function from the current state to the next state. The cost/benefit is the absence of shared global state. My continuation is different from your continuation. The alternative is to determine the next state synchronously with the invocation of the transition function for the next state by reading a shared state. If I invoke the transition function at time t1 I will get the same result as you would get if you invoked the transition function at t1...assuming of course that we did not both invoke it at the same time [then it's just a matter of convention as to who gets what].