Comment by JonChesterfield
1 day ago
> Loko’s runtime uses concurrency based on Concurrent ML.
That one could be a big deal.
https://scheme.fail/manual/loko.html#Concurrency
The docs don't mention channels and say that fibres are built on limited continuations (call/cc) which suggests missing some of the clever stuff in CML (e.g. that threads deadlocked on a channel get garbage collected)
While being heavily inspired guile-fibers, it seems to not actually be parallel.
Anyway, I would say it is actually the nicest way to write concurrent programs. It supports you and helps you to not shoot yourself in the foot, while also staying out of the way.