Blog
The OCaml Planet
Articles and videos contributed by both experts, companies and passionate developers from the OCaml community. From in-depth technical articles, project highlights, community news, or insights into Open Source projects, the OCaml Planet RSS feed aggregator has something for everyone.
Want your Blog Posts or Videos to Show Here?
To contribute a blog post, or add your RSS feed, check out the Contributing Guide on GitHub.
With the release of Irmin 2.0.0, we are happy to announce a new package - irmin-graphql, which can be used to serve data from Irmin over…
We are pleased to announce Irmin 2.0.0, a major release of the Git-like distributed branching and storage substrate that underpins MirageOS…
OCaml has a well-deserved reputation for compiling quickly. This is thanks in part to its uniform representation: all values have the same memory layout, so generic code does not need to be specialized and recompiled for each use. This uniformity has a downside: some programs waste a lot of time converting back and forth to this uniform representation. In this talk, I’ll describe some work-in-progress to remove this overhead, by extending OCaml’s type system to allow other memory layouts, giving the programmer more fine-grained control over how code is compiled. Stephen is a programming languages researcher and OCaml core developer on Jane Street's Tools and Compilers team. Prior to that, he worked at OCaml Labs, did a PhD on subtyping, and wrote jq. His hobbies include hiking, cooking, and writing about himself in the third person.
OCaml has a well-deserved reputation for compiling quickly. This is thanks in part to its uniform representation: all values have the same memory layout, so generic code does not need to be specialized and recompiled for each use. This uniformity has a downside: some programs waste a lot of time converting back and forth to this uniform representation. In this talk, I’ll describe some work-in-progress to remove this overhead, by extending OCaml’s type system to allow other memory layouts, giving the programmer more fine-grained control over how code is compiled. Stephen is a programming languages researcher and OCaml core developer on Jane Street's Tools and Compilers team. Prior to that, he worked at OCaml Labs, did a PhD on subtyping, and wrote jq. His hobbies include hiking, cooking, and writing about himself in the third person.
This blog post is an introduction on how to setup a library available for both BuckleScript and OCaml, sharing as much code as possible.