Ok. Re-reading your article, I understand what's t...

# arrow

[melatonina]

Ok. Re-reading your article, I understand what's the issue in what I'm doing. You provided an implementation of concurrency:
"Arrow-fx is the name of the concurrency/effects library by the Arrow team. It stands as a compatible alternative to kotlinx.coroutines by Jetbrains. It features most of the core constructs necessary for sequencing, parallelism, cancellation, threading, resource management, async error handling, plus clock and atomic operations."
My abstraction is a cheap layer on top of kotlin `Flow`s. I'm working one or two abstraction levels above coroutines: kotlin `Flow`s are probably based on `Channel`s which are based on coroutines. And Arrow currently don't have anything like that.
Maybe I should try and implement something like Flows using Arrow-fx, and that would work nicely with your API. It's just an intuition, so pardon me if it's something silly. I have to fiddle with code to get a better idea. Do you see anything wrong in what I'm saying?