farolero VS cloroutine

You can use this library to get CL-style conditions and restarts in Clojure: https://github.com/IGJoshua/farolero

True, the CL REPL is more useful than the Clojure REPL, but CL has a 20-30 year head start in development. Plus, Clojure was developed as a hosted language, and runs on .NET, Javascript, JVM, and even Dart (in-progress).

Since exceptions are quite deeply integrated into those platforms (as opposed to conditions), it has "bled through" to the Clojure APIs, and, in turn, REPL.

Folks have written a CL-style condition/restart library for Clojure (https://github.com/IGJoshua/farolero) too.

conditions/restarts are also a possibility https://github.com/IGJoshua/farolero

Someone added conditions/restarts to Clojure: https://github.com/IGJoshua/farolero

It does allow errors to be caught by the Repl and just.hkw to handle them.

farolero

This is interesting tool[1] that allows much the same with Clojure

[1]: https://github.com/IGJoshua/farolero

https://github.com/IGJoshua/farolero This uses derive hierarchies to enable general error handling.

Thanks for sharing! I think these restarts could definitely be implemented as a library in Clojure with the help of a coroutine library like https://github.com/leonoel/cloroutine#guides

Do you mean the example here https://github.com/leonoel/cloroutine/blob/master/doc/01-generators.md , with the `*tail* binding? It took me a long time looking at it to finally grok it, and it's really hard to explain in English but basically when the coroutine comes across one of these symbols that are "breaks" (in our case, "yield" is such a breaking symbol), then it will pause the coroutine, and actually call what the symbol points to (the implementation of "yield"), which returns (cons x *tail*), and keep in mind that it is all run within a recursive call to gen-seq where *tail* is bound to a lazy-seq of the remainder of the generator (binding [*tail* (gen-seq gen)] (gen)), it's pretty confusing but yeah just have to stare at it for a long time I think haha.

I think Clojure is really missing python/js-style generators, like what is implemented in https://github.com/leonoel/cloroutine/blob/master/doc/01-generators.md

The next level up is core.async go blocks which compile your AST to a state machine. Also see cloroutine which also compiles the AST to a state machine or something, one of the tutorials uses cloroutine to add async/await to Clojure.

Coroutines are a more general concept, and can be used to implement conditions/delimited continuations. There’s an example in their docs.