eioio
RFCs
Our great sponsors
eioio | RFCs | |
---|---|---|
25 | 3 | |
502 | 142 | |
2.6% | -0.7% | |
9.1 | 0.0 | |
7 days ago | 26 days ago | |
OCaml | ||
GNU General Public License v3.0 or later | - |
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
-
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
-
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.
-
Why OCaml?
Here's an example using OCaml 5 to run multiple fibers concurrently (look - no monads!):
-
OCaml 5.0 Alpha Release
Effects are included in OCaml 5, but considered experimental. This doesn't stop us from building libraries that take advantage of them internally, in order to provide really nice external interfaces.
The best developed one is "eio", which uses effects (and io_uring on Linux) internally in order to provide a really high performance, direct-style IO library for OCaml. You can walk through some of the code here: https://github.com/ocaml-multicore/eio#getting-started
Also a video talk about our experiences with using effects for writing parsers, from the OCaml Workshop last year. https://watch.ocaml.org/videos/watch/74ece0a8-380f-4e2a-bef5...
-
Soupault 4.0.0: as extensible as Jekyll, still statically linked
Its a good time to try it. The tooling has come a long way and OCaml has an excellent build system [1] (dune is probably the best build tool I've used and I miss it whenever I use other programming languages), excellent editor tooling for vscode [2], emacs and neovim. OCaml 5.0 will bring multicore support [3] and an effect system that will cover a lot of interesting use-cases. As an example with OCaml 5 it'll be feasible to have concurrency libraries that still let you write in direct-style [4] [5]. I don't intend to say that OCaml will fit every use-case, but there is a lot going for it even in its current form before multicore support lands. If you want a language that compiles fast (it does compile really fast, at-part with Go if not better), has excellent performance characteristics, and has a good story for concurrency, you should give OCaml a chance!
[2] https://marketplace.visualstudio.com/items?itemName=ocamllab...
[3] https://discuss.ocaml.org/t/the-road-to-ocaml-5-0/8584
[4] https://github.com/ocaml-multicore/eio
[5] https://github.com/anuragsoni/sandbox/tree/main/ocaml/effect...
RFCs
-
Why are imperative programs considered faster than their functional counterparts?
A middle ground between uniform representation and specializing for every type is specializing for every data layout. See the unboxed types RFC for OCaml.
-
PR to Merge Multicore OCaml
For both 2 and 3 you may find https://github.com/ocaml/RFCs/blob/unboxed-types/rfcs/unboxe... very interesting. I'm hoping that progresses beyond the RFC stage.
What are some alternatives?
ocaml-multicore - Multicore OCaml
loom - Concurrency permutation testing tool for Rust.
roast - 🦋 Raku test suite
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
virt-v2v - Virt-v2v converts guests from foreign hypervisors to run on KVM
dune - A composable build system for OCaml.
ocaml-aeio - Asynchronous effect based IO