4 ms·
never say never, i think maybe can be done with modifications to missionary, a structured concurrency dsl implementing process supervision for clojure/script. w
by dustingetz 3y ago
never say never, i think maybe can be done with modifications to missionary, a structured concurrency dsl implementing process supervision for clojure/script. we already instrument missionary flows for testing missionary itself (asserting its state transitions)
- j16sdiz 3y agowell.. that is just a fancy way to insert synchronisation point. we useful, but not something limit breaking
- kiitos 3y agoI guess you're suggesting that you can build an abstraction layer (I guess you're calling it missionary) which (a) can reliably intermediate every interaction between a user program and any potentially non-deterministic API, and (b) can be configured at runtime as synchronous/serial/deterministic or async/concurrent/non-deterministic. Is this accurate? (If so, I'm pretty confident that this is infeasible.)
- dustingetz 3y agoElectric Clojure backends already get such effect supervision for free (you'll need to manually tag sync/blocking effects). https://github.com/hyperfiddle/electric https://github.com/hyperfiddle/electric https://github.com/leonoel/missionary https://github.com/leonoel/missionary
- kiitos 3y ago> you'll need to manually tag sync/blocking effects Well, that's the hard part, so if I need to do it myself, your library isn't providing much value.