monad-par
monad-par copied to clipboard
simonmar
See notes in `ParTests.hs`. This is only an issue with the `Direct` scheduler, and seems to emerge from the attempt to catch errors on worker threads. Trace doesn't bother, and...
This is the issue i reported in Criterion https://github.com/bos/criterion/issues/28 and mistakenly in an older closed monad-par ticket. Likely hit via Criterion calling the following function in Statistics that is the...
The title says it all: ``` [distmeta_M ThreadId 6] [rcvdmn] RUNNING STOLEN PAR WORK Exception inside child thread "Daemon thread (ReceiveDaemon)": stack overflow Stack space overflow: current size 8388608 bytes....
This has been a big dependency liability and is one of the things causing trouble for full GHC 7.6 compliance.
The current `ParFuture` type class is parameterized with both the monad `m` and the `future`. Since the only operation that can be applied to a `future` is `get` why not...
From a Safe Haskell perspective, the following combination is safe: ``` haskell instance MonadIO Par runParIO :: Par a -> IO a ``` However, if this instance exists alongside `runPar...
One strategy is to organize workers into a tree such that each worker only listens to its parent and only signals its children to switch from active work-stealing to idle...
Related to Issue #9: The monad-par package currently provides a "parMap" for everything traversable. Sadly, this is woefully inefficient for data structures like arrays and Data.Vector, which can directly support...
I worry about the API having too many convenience routines with put vs. put_ and { fork, spawn, spawn_, pval }.
At least in SHORTRUN=1 mode. Presently, [2011.10.20] it runs timings but does not verify the correctness of the answers that come back.