TOtoolslive·May 13, 2021
thx!
Another question. Suppose you're starting from scratch, is it worth going the effects based async io route ?
https://github.com/kayceesrk/ocaml-aeio
seems very interesting...
In Multicore OCaml: April 2021kayceesrk
ocaml-aeio
OCaml2020–2021
kayceesrk / ocaml-aeio
ocaml-aeio
Asynchronous effect based IO
2Distinct people
2Mentions
0Explicit recommenders
32GitHub stars
What to know before exploring
What it is
Asynchronous effect based IO
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month2 dated mentions
Observed mentions: 2020-03-31 05:40:47 UTC to 2021-05-13 16:04:08 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 2020 | 2020-03-01 00:00:00 UTC | 2020-04-01 00:00:00 UTC | 1 | 0 | 1 |
| Apr 2020 | 2020-04-01 00:00:00 UTC | 2020-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2020 | 2020-05-01 00:00:00 UTC | 2020-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2020 | 2020-06-01 00:00:00 UTC | 2020-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2020 | 2020-07-01 00:00:00 UTC | 2020-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2020 | 2020-08-01 00:00:00 UTC | 2020-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2020 | 2020-09-01 00:00:00 UTC | 2020-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2020 | 2020-10-01 00:00:00 UTC | 2020-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2020 | 2020-11-01 00:00:00 UTC | 2020-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2020 | 2020-12-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2021 | 2021-01-01 00:00:00 UTC | 2021-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2021 | 2021-02-01 00:00:00 UTC | 2021-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2021 | 2021-03-01 00:00:00 UTC | 2021-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2021 | 2021-04-01 00:00:00 UTC | 2021-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2021 | 2021-05-01 00:00:00 UTC | 2021-06-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources(I work on Multicore OCaml)
Multicore OCaml separates the notion of concurrency (overlapped execution) and parallelism (simultaneous execution). You can have one without the other but also have both. The main principle that we're going for is that the compiler should expose just enough support for concurrency and parallelism such that interesting features can live outside the compiler as libraries. This permits the library evolution not to be tied with the language evolution but also permits diversity of libraries beyond what the language developers can aim to achieve. That said, we will build and maintain a few core libraries for concurrency and parallelism.
For concurrency, Multicore OCaml exposes effect handlers [1,2,3] which allows you to build generators, async/await, coroutines, etc as library functions (as opposed to primitives nat
Read the rest
ively supported by the compiler). For example, have a look at aeio [4] which permits the construction of scalable asynchronous I/O in direct-style (no callbacks). aeio is also discussed in [1]. We also plan to extend Lwt to support parallelism.
For parallelism, the compiler exposes Domains, which are a wrapper over OS-threads [5]. Domains expose a low-level API that is not suitable for end user consumption. On top of domains, we support channels with bounded buffers [6] (similar to channels in Go, Mvars in GHC Haskell) as well as software transactional memory (STM) that supports shared memory and message passing concurrency and which can take advantage of hardware transactional memory [7].
[1] Concurrent System Programming with Effect Handlers: http://kcsrk.info/papers/system_effects_feb_18.pdf
[2] CUFP effects tutorial: https://github.com/ocamllabs/ocaml-effects-tutorial
[3] Effects Examples: https://github.com/kayceesrk/effects-examples
[4] Aeio: Asynchronous Effect-based IO https://github.com/kayceesrk/ocaml-aeio
[5] Domains: https://github.com/ocaml-multicore/ocaml-multicore/blob/para...
[6] domainslib: https://github.com/ocaml-multicore/domainslib
[7] Reagents: https://github.com/ocaml-multicore/reagents