3 ms·
The mention of making CPS (continuous passing style) compiler integration possible is something very important. That would enable Go- or Kotlin-like coroutines
by red_vodka 3y ago
The mention of making CPS (continuous passing style) compiler integration possible is something very important. That would enable Go- or Kotlin-like coroutines to land in the language, which is sorely needed to end the async wars between stdlib's horrible asyncdispatch module, and Status.im's barely documented Chronos async/await implementation.
- throwmeouthn 3y ago[dead]
- zevv 3y agoThere has been a more-or-less working CPS implementation for Nim for a few years now: https://github.com/nim-works/cps https://github.com/nim-works/cps https://github.com/nim-works/cps/tree/master/docs https://github.com/nim-works/cps/tree/master/docs Nobody seems to care though, as it has gained no traction at all and it has been mostly ignored by the core team.
- red_vodka 3y agoThe issue with the CPS implementation here is that the compile times are too slow, and there are several restrictions due to flaws and limitations of the compiler. That's the reason CPS in the compiler is a big deal. I've used the CPS lib you're showing before, and it's very nice, but the compile times make it absolutely useless for productive development.