dotfiles
cloroutine
dotfiles | cloroutine | |
---|---|---|
1 | 11 | |
7 | 226 | |
- | - | |
9.0 | 2.4 | |
9 days ago | about 2 months ago | |
Emacs Lisp | Clojure | |
- | Eclipse Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles
-
ClojureRS – Clojure interpreter implemented in Rust
Extremely useful. I use it to write small to medium scripts, replacing Bash. For example, I wrote a small client that interacts with Pocket API. [1] Aside from interop with shell commands (I use Fish for that), most things seem pleasant so far.
[1] https://github.com/hiepph/dotfiles/blob/master/scripts/_pock...
cloroutine
-
ClojureRS – Clojure interpreter implemented in Rust
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
-
GitHub - leonoel/cloroutine: Coroutine support for clojure
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.
-
CLJ-2555: clojure.core/iteration · clojure/clojure@e45e478
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
-
Real-life use cases for CLJS macros
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.
- Continuations in Clojure
- 6 Years of Professional Clojure
-
Common Lisp Style Conditions+Restarts in Clojure
Coroutines are a more general concept, and can be used to implement conditions/delimited continuations. There’s an example in their docs.
What are some alternatives?
ClojureRS - Clojure, implemented atop Rust (unofficial)
zio-schema - Compositional, type-safe schema definitions, which enable auto-derivation of codecs and migrations.
farolero - Thread-safe Common Lisp style conditions and restarts for Clojure(Script) and Babashka.
babashka - Native, fast starting Clojure interpreter for scripting
core.async - Facilities for async programming and communication in Clojure
clojure-scheme - Clojure to Scheme to C to the bare metal.
await-cps - async/await for continuation-passing style functions
pure-conditioning - A simple, fast, purely functional condition / restart system for Clojure.
promesa - A promise library & concurrency toolkit for Clojure and ClojureScript.
missionary - A functional effect and streaming system for Clojure/Script