clojure-scheme VS cloroutine

For me it's microcontrollers, however I've heard in spite of the unmaintained status, clojure-scheme[1] is very usable. It uses gambit to produce C-code you can compile anywhere.

https://github.com/takeoutweight/clojure-scheme

> But wouldn't it make more sense to first rewrite Clojure itself in some small/minimal scheme-y subset of Clojure

How about Scheme?: https://github.com/takeoutweight/clojure-scheme

Note that this project is unmaintained and the last updates are ~10 years old.

lokke seems to use Guile's tooling (compiler tower, to be specific) to compile clojure-esque code to objects understood by said Guile's tooling. This is a little different from Clojurescript's approach which use ClojureJVM to transpile to javascript. There was actually another Clojure to Scheme project that leverages Clojurescript JVM transpiler: https://github.com/takeoutweight/clojure-scheme - It targets Gambit scheme instead of Guile

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.