mtl77

3 ms·

1. 1.▲
   by mtl77 3y ago

   Main reasons at the time: * strictness was preferred for consistency 1) with the C++ execution model (a lot of our code base is written in C++ by quants, and a typical Mu program will make extensive use of these external calls; they can eve
2. 2.▲
   by mtl77 3y ago

   The reason is that we don't have a general solution for tail-call optimisation for computations made of a mixture of Mu code and C++ primitives. We have higher order functions defined in C++ that can be called from Mu, and can call bac
3. 3.▲
   by mtl77 3y ago

   Gergo and I are working on a new implementation of the Mu compiler that uses GHC up to Core; from which we translate to the legacy Mu bytecode format. The original Mu compiler is not designed for separate compilation, our new version is, ba