# Dune and Multicore

**URL:** <https://discuss.ocaml.org/t/dune-and-multicore/3315>\
**Category:** Community\
**Tags:** multicore, dune\
**Created:** [February 10, 2019, 4:49am UTC](https://discuss.ocaml.org/t/dune-and-multicore/3315 "2019-02-10T04:49:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![jhw](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/jhw/32/1639_2.png) [@jhw](https://discuss.ocaml.org/u/jhw)\
**Post date:** [February 10, 2019, 4:49am UTC](https://discuss.ocaml.org/t/dune-and-multicore/3315/1 "2019-02-10T04:49:57Z")

</div>

For grins, I updated my _multicore_ OPAM switch and started looking into what is currently keeping my Orsetto project from compiling there. At the moment, the answer is that Dune doesn’t compile. Which I suppose is not really noteworthy, because multicore is still way way off, but I was vastly amused by the log message that appeared on my console:

> I must not segfault. Uncertainty is the mind-killer. Exceptions are the little-death that brings total obliteration. I will fully express my cases. Execution will pass over me and through me. And when it has gone past, I will unwind the stack along its path. Where the cases are handled there will be nothing. Only I will remain.

I don’t know who wrote this, but it has me rolling on the floor— especially given the irony of this happening on a compiler that’s trying to introduce algebraic effects. Just wanted to raise a glass for that here. Bravo, whoever you are. You have won the Internet today.

---

_[View the full topic](https://discuss.ocaml.org/t/dune-and-multicore/3315)._