continuation

JavaScript generators are unmined gold! We've done a lot of usage of JavaScript generators as delimited continuations; using them to implement the classic shift/reset operations in JavaScript. https://github.com/thefrontside/continuation Built on those delimited continuations is structured concurrency for JavaScript (https://frontside.com/effection)

Further, there is a delimited continuation library that effection uses: https://github.com/thefrontside/continuation

While working on effection@v3 (https://github.com/thefrontside/effection) we spent a bunch of time ensuring that our delimited continuations could handle deep recursive call stacks in Deno. PR: https://github.com/thefrontside/continuation/pull/11 TCO would have definitely simplified this issue. What’s worse is hitting maximum memory callstack exception is very tricky to catch and is not reliable across runtimes. So when a user hits it it can be tricky to track down.

redux-saga maintainer here! Before async/await, generators were the only way to express async flow control in a synchronous way. Libraries like “co” were really popular at the time. There are some really downside to async/await which is why redux-saga continued to use generators. Even in 2023, me and a couple others are experimenting with deliminited continuations using generators as the foundation. A couple of libraries we have built: - https://github.com/thefrontside/continuation - https://github.com/thefrontside/effection/tree/v3 - https://github.com/neurosnap/starfx The last one intends to replace redux-saga using DCs. Here’s a presentation I gave recently talking about DCs in typescript: https://youtu.be/uRbqLGj_6mI?si=XI0JNMKMoO2VHMvM

These libraries rely on deliminited continuations: https://github.com/thefrontside/continuation Because of this tiny implementation we are able to express any async flow construct with less code than relying on something like async/await or callbacks.