| ▲ | fiddlerwoaroof 8 hours ago | |
Every several years people reinvent serializable continuations | ||
| ▲ | gunnarmorling 8 hours ago | parent | next [-] | |
Yupp, making that same point in the post :) > You could think of [Durable Execution] as a persistent implementation of the memoization pattern, or a persistent form of continuations. | ||
| ▲ | andersmurphy 8 hours ago | parent | prev | next [-] | |
Haha so true. Shame image based programming never really caught on. Janet lang lets you serialize coroutines which is fun. Make this sort of stuff trivial. | ||
| ▲ | rileymichael 5 hours ago | parent | prev | next [-] | |
unfortunately they've never really taken off so folks reach for explicit state machines instead. there have been a handful of options on the jvm over the years (e.g. quasar, kilim) but they're all abandoned now, the loom continuation API is internal with no hint of it becoming public, kotlin's aren't serializable and the issue is inactive (https://github.com/Kotlin/kotlinx.coroutines/issues/76), etc.. such a shame | ||
| ▲ | smitty1e 7 hours ago | parent | prev [-] | |
Is this reinvention somehow "transactional" in nature? | ||