The OCaml Planet

SmartPy is a complete system to develop smart-contracts for the Tezos blockchain. It is an embedded EDSL in python to write contracts and their test scenarios. It includes an online IDE, a chain explorer, and a command-line interface. Python is us...

OCaml-CI is a CI service for OCaml projects. It uses metadata from the project’s opam and dune files to work out what to build, and uses caching to make builds fast. It automatically tests projects against multiple OCaml versions and OS platforms...

OCaml-CI1 is a CI service for OCaml projects. It uses metadata from the project’s opam and dune files to work out what to build, and uses caching to make builds fast. It automatically tests projects against multiple OCaml versions and OS platforms...

Slides, speaker notes and runnable examples mentioned in this talk are available at: https://github.com/ocaml-multicore/ocaml2020-workshop-parallel With the availability of multicore variants of the recent OCaml versions (4.10 and 4.11) that main...

This talk covers: - Integrated Development Environments - Next Steps for the OCaml Platform - Plans for 2020-2021

This proposal describes a presentation to be given at the OCaml’20 workshop. The presentation will cover a new OCaml filesystem, ImpFS, and the related libraries. The filesystem makes use of a B-tree library presented at OCaml’17, and a key-value ...

Rendering OCaml document is widely known as a very difficult task: The ever-evolving OCaml module system is extremely rich and can include complex set of inter-dependencies that are both difficult to compute and to render in a concise document. It...

Coda is a new cryptocurrency that uses zk-SNARKs to dramatically reduce the size of data needed by nodes running its protocol. Nodes communicate in a format automatically derived from type definitions in OCaml source files. As the Coda software ev...

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.