speculation (hackage): A framework for safe, programmable, speculative parallelism, loosely based on:  Prakash Prabhu, G. Ramalingam, and Kapil Vaswani, "Safe Programmable Speculative Parallelism", In the proceedings of Programming Language Design and Implementation (PLDI) Vol 45, Issue 6 (June 2010) pp 50-61. http://research.microsoft.com/pubs/118795/pldi026-vaswani.pdf  This package provides speculative function application and speculative folds. Speculative STM transactions take the place of the transactional rollback machinery from the paper.  For example:  spec g f a evaluates f g while forcing a, if g == a then f g is returned, otherwise f a is evaluated and returned. Furthermore, if the argument has already been evaluated, we skip the f g computation entirely. If a good guess at the value of a is available, this is one way to induce parallelism in an otherwise sequential task. However, if the guess isn't available more cheaply than the actual answer, then this saves no work and if the guess is wrong, you risk evaluating the function twice. Under high load, since 'f g' is computed via the spark queue, the speculation will be skipped and you will obtain the same answer as 'f $! a'.  The best-case timeline looks like:  The worst-case timeline looks like:  Note that, if f g takes longer than a to compute, in the HEAD release of GHC, f g will be collected and killed during garbage collection.  Under high load:  Compare these to the timeline of f $! a:  specSTM provides a similar time table for STM actions, but also rolls back side-effects. The one unfortunate operational distinction is that it is forced to compute a in the background thread and therefore degrades slightly less gracefully under load, although we mitigate this effect by only enqueuing if the number of sparks for the current capability is lower than the total number of capabilities, to try to avoid wasting time when all computational resources are in use.
Keywords: bsd3|concurrency|library