nominolo

13 ms·

1. 1.▲
   by nominolo 15y ago

   Here's some related work from 2005: http://www.google.co.uk/search?ie=UTF-8&q=%22A+Nitpicker...
2. 2.▲
   by nominolo 16y ago

   GHC has a comparatively expensive write barrier. That could be seen as taking advantage of immutability. The runtime system takes more advantage of purity, though. For example, it's safe to have certain races, because they will give the
3. 3.▲
   by nominolo 16y ago

   Incidentally fusion won't work for this example (at least not as currently implemented.) Only `foldr` is fusable. Fortunately, regular inlining does just fine. There is of course an even simpler version: sum (map face_value dice)
4. 4.▲
   by nominolo 16y ago

   No, the problem with Itanium is/was that it's no-one knew how to write good compilers for them. Also, VLIW is incredibly close to the hardware and thus bound to be outdated very quickly. It didn't help that IA64 has about 40bits / instruc
5. 5.▲
   by nominolo 17y ago

   JIT simply stands for Just-in-time compilation or optimisation, that is you delay optimising parts of your program until the program executes. Most systems start of by interpreting the some form of bytecode and observe which parts are execu
6. 6.▲
   by nominolo 17y ago

   A closure is a function + environment, i.e., the values of its free variables at the time of creation. A thunk is a suspended computation together with an environment. That is, a thunk is a special type of closure, where the function takes