ocaml-multicore
dune
ocaml-multicore | dune | |
---|---|---|
8 | 27 | |
763 | 1,536 | |
0.0% | 1.0% | |
0.0 | 9.9 | |
over 1 year ago | 7 days ago | |
OCaml | OCaml | |
GNU General Public License v3.0 or later | MIT 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.
ocaml-multicore
-
PR to Merge Multicore OCaml
1. Domains are the unit of parallelism. A domain is essentially an OS thread with a bunch of extra runtime book-keeping data. You can use Domain.spawn (https://github.com/ocaml-multicore/ocaml-multicore/blob/5.00...) to spawn off a new domain which will run the supplied function and terminate when it finishes. This is heavyweight though, domains are expected to be long-running.
2. Domainslib is the library developed alongside multicore to aid users in exploiting parallelism. It supports nested parallelism and is pretty highly optimised (https://github.com/ocaml-multicore/domainslib/pull/29 for some graphs/numbers). The domainslib repo has some good examples: https://github.com/ocaml-multicore/domainslib/tree/master/te...
3. We've not tested against other forms of parallelism. There isn't anything stopping you exploiting SIMD in addition to parallelism from domains.
4. No, we've not compared performance by OS.
5. No plans for the multicore team to look at accelerator integration at the moment.
-
Will rust ever have a futures executor in std?
For Algebraic Effects and Multicore OCaml specifically, I have this intro saved and they've been publishing regular updates here's October's. They have a paper linked from their repo's README but I don't remember the contents offhand.
-
Graydon Hoare: What's next for language design? (2017)
Until recently Multicore OCaml was focused on deep handlers. The people working on the formalization of effects (either for program proofs or typed effects) were quite keen to have shallow handler integrated however. Thus, the effect module of the OCaml 5 preview contains both (see https://github.com/ocaml-multicore/ocaml-multicore/blob/5.00...) since September. I fear that non-academic literature has not followed this change (on the academic side, see https://dl.acm.org/doi/10.1145/3434314 for a program proofs point of view).
-
Multicore OCaml: September 2021, effect handlers will be in OCaml 5.0
Yes, it's announcing that the next but one version, 5.0, will support multicore and effect handlers.
For what it's worth you can actually start using Multicore OCaml today, there are installation instructions on the wiki: https://github.com/ocaml-multicore/ocaml-multicore
-
Aren't green threads just better than async/await?
ocaml-multicore/ocaml-multicore
-
Multicore OCaml: April 2021
Could you explain (in simple terms if possible) how the Multicore OCaml achieves a memory model which is much simpler on more efficient than in Java or C (mentioned at https://github.com/ocaml-multicore/ocaml-multicore/wiki)?
Didn't see any mentions of critical sections (mutexes) with C++ examples in the documentation ("Bounding Data Races in Space and Time"). I'm not sure I understand the comparisons the writers are presenting.
-
Multicore OCaml: Dec 2020 / Jan 2021
There are getting started instructions up on https://github.com/ocaml-multicore/ocaml-multicore
dune
-
Tagging OCaml packages
If you are using the dune build system, add the tag(s) to your dune-project file's package stanza. E.g.:
-
NextJS, the App Router and ReasonReact
One way to get around this is to modify the api/dune file with (include_subdirs qualified); this means that every subdirectory of api/ can be referenced by module namespacing and we don't have to write dune files for every route (or pages) folder. However, the OCaml LSP does not like it and red squiggles will show up in the editor (although the app with still compile without errors). Trying to develop the app knowing those red squiggles cannot be vanquished would drive me nuts, so instead of using (include_subdirs qualified) I just wrote dune files for every route (and page) which gets rid of the red squiggles.
-
Generating .ml test cases from a glob of text files in a directory using dune
2) Neither would having all source/targets specified, as that would entail listing them all in the dune file as wildcard rules is apparently still not a thing: https://github.com/ocaml/dune/issues/307
-
Dune build
There is a small example on the dune home page: https://dune.build/
- The YAML Document from Hell
-
Ask HN: Programs that saved you 100 hours? (2022 edition)
Dune (https://dune.build/) is the preeminent build tool for OCaml development. I don't love its input syntax (s-expressions), and I sometimes miss the ability to write high-level functions to reduce boilerplate (especially for unit tests), but it always gets the dependencies right, and it's fast. This is in stark contrast to some of my experiences with various other build systems, and I am super happy that the default option for OCaml build systems is so good.
- Help getting started with Ocaml
-
Faster Incremental Builds with Dune 3
It's still weird because dune's own site only makes Jane Street references: https://dune.build/.
-
How to print anything in OCaml
ONE of the big benefits of OCaml is its powerful REPL (also called the toplevel), the interactive command-line utility where you can load modules, type in and execute code, and see its results. The modern REPL, utop, has powerful auto-completion and integration with the build system dune, which enables productive workflows like loading an entire project's libraries in the REPL and interactively exploring them.
- Dune 3.2.0
What are some alternatives?
eioio - Effects-based direct-style IO for multicore OCaml
statsd-filter-proxy-rs - A filter proxy for StatsD
domainslib - Parallel Programming over Domains
opam - opam is a source-based package manager. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow.
roast - 🦋 Raku test suite
ocaml - The core OCaml system: compilers, runtime system, base libraries
enso - Hybrid visual and textual functional programming.
CorrinoEngine - CorrinoEngine is an open-source project which will recreate the Emperor : Battle for Dune
bumpalo - A fast bump allocation arena for Rust
loom - Concurrency permutation testing tool for Rust.
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason