eioio
ocaml-aeio
Our great sponsors
eioio | ocaml-aeio | |
---|---|---|
25 | 1 | |
517 | 33 | |
4.1% | - | |
9.0 | 0.0 | |
3 days ago | almost 3 years ago | |
OCaml | OCaml | |
GNU General Public License v3.0 or later | ISC License |
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.
eioio
-
Eio 1.0 Release: Introducing a new Effects-Based I/O Library for OCaml
the actual project (Readme has some code samples): https://github.com/ocaml-multicore/eio
-
OCaml: a Rust developer's first impressions
For 5.0+ you might want to look at https://github.com/ocaml-multicore/eio for how effects can make async much more pleasant
- Alternatives to scala FP
-
How Much Memory Do You Need to Run 1 Million Concurrent Tasks?
Great post! I would love to see this extended to OCaml 5 (with eio) and Haskell
- Eio -- Effects-Based Parallel IO for OCaml
-
OCaml 5.0.0: multicore support and effect handlers for OCaml
Second, effects enable a new style of concurrency libraries like eio that forgoes the need to wrap every asynchronous computation in a monad.
- OCaml 5.0 Multicore is out
-
What’s so great about functional programming anyway?
> This is realllly unidiomatic in real world Haskell.
Whether idiomatic or not does not matter. It proves my point:
IO won't save you, and even very mundane effects are not part of the game…
Idris is the "better Haskell" sure, but the effect tracking is still part of the uncanny valley (still IO monad based).
Koka is a toy, and Frank mostly "only a paper" (even there is some code out there).
The "Frank concept" is to some degree implemented in the Unison language, though:
https://www.unison-lang.org/learn/fundamentals/abilities/
Having a notion of co-effects (or however you please to call them) is imho actually much more important than talking about effects (as effects are in fact neither values nor types—something that all the IO kludges get wrong).
I think the first practicable approach in the mainstream about this topic will be what gets researched and developed for Scala. The main take away is that you need to look at things form the co-effects side first and foremost!
In case anybody is interested in what happens in Scala land in this regard:
https://www.slideshare.net/slideshow/embed_code/key/aLE9M37d...
https://docs.scala-lang.org/scala3/reference/experimental/cc...
But also the development in OCaml seems interesting:
https://github.com/ocaml-multicore/eio#design-note-capabilit...
Look mom, "effects", but without the monad headache!
-
Practical OCaml, Multicore Edition
To enable access to all these features, an exciting new library called Eio is being developed. It uses a new paradigm of direct-style concurrent I/O programming, without the need for monads or async/await, thus avoiding the function colour problem.
ocaml-aeio
What are some alternatives?
ocaml-multicore - Multicore OCaml
roast - 🦋 Raku test suite
loom - Concurrency permutation testing tool for Rust.
virt-v2v - Virt-v2v converts guests from foreign hypervisors to run on KVM
domainslib - Parallel Programming over Domains
rescript-compiler - The compiler for ReScript.
effects-examples - Examples to illustrate the use of algebraic effects in Multicore OCaml
weave - A state-of-the-art multithreading runtime: message-passing based, fast, scalable, ultra-low overhead
ocaml - The core OCaml system: compilers, runtime system, base libraries