/usr/share/doc/libghc-monad-par-doc/html/monad-par.txt is in libghc-monad-par-doc 0.3.4.8-3build3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 | -- Hoogle documentation, generated by Haddock
-- See Hoogle, http://www.haskell.org/hoogle/
-- | A library for parallel programming based on a monad
--
-- The <a>Par</a> monad offers a simple API for parallel programming. The
-- library works for parallelising both pure and <tt>IO</tt>
-- computations, although only the pure version is deterministic. The
-- default implementation provides a work-stealing scheduler and supports
-- forking tasks that are much lighter weight than IO-threads.
--
-- For complete documentation see <a>Control.Monad.Par</a>.
--
-- Some examples of use can be found in the <tt>examples/</tt> directory
-- of the source package.
--
-- Other related packages:
--
-- <ul>
-- <li><tt>abstract-par</tt> provides the type classes that abstract over
-- different implementations of the <tt>Par</tt> monad.</li>
-- <li><tt>monad-par-extras</tt> provides extra combinators and monad
-- transformers layered on top of the <tt>Par</tt> monad.</li>
-- </ul>
--
-- Changes in 0.3.4 relative to 0.3:
--
-- <ul>
-- <li>Fix bugs that cause "thread blocked indefinitely on MVar"
-- crashes.</li>
-- <li>Added <a>Control.Monad.Par.IO</a></li>
-- </ul>
@package monad-par
@version 0.3.4.8
-- | This module exposes the internals of the <tt>Par</tt> monad so that
-- you can build your own scheduler or other extensions. Do not use this
-- module for purposes other than extending the <tt>Par</tt> monad with
-- new functionality.
module Control.Monad.Par.Scheds.TraceInternal
data Trace
Get :: (IVar a) -> (a -> Trace) -> Trace
Put :: (IVar a) -> a -> Trace -> Trace
New :: (IVarContents a) -> (IVar a -> Trace) -> Trace
Fork :: Trace -> Trace -> Trace
Done :: Trace
Yield :: Trace -> Trace
LiftIO :: (IO a) -> (a -> Trace) -> Trace
data Sched
Sched :: {-# UNPACK #-} !Int -> IORef [Trace] -> IORef [MVar Bool] -> [Sched] -> Sched
[no] :: Sched -> {-# UNPACK #-} !Int
[workpool] :: Sched -> IORef [Trace]
[idle] :: Sched -> IORef [MVar Bool]
[scheds] :: Sched -> [Sched]
newtype Par a
Par :: ((a -> Trace) -> Trace) -> Par a
[runCont] :: Par a -> (a -> Trace) -> Trace
newtype IVar a
IVar :: (IORef (IVarContents a)) -> IVar a
data IVarContents a
Full :: a -> IVarContents a
Empty :: IVarContents a
Blocked :: [a -> Trace] -> IVarContents a
-- | The main scheduler loop.
sched :: Bool -> Sched -> Trace -> IO ()
-- | Run a parallel, deterministic computation and return its result.
--
-- Note: you must NOT return an IVar in the output of the parallel
-- computation. This is unfortunately not enforced, as it is with
-- <tt>runST</tt> or with newer libraries that export a Par monad, such
-- as <tt>lvish</tt>.
runPar :: Par a -> a
-- | A version that avoids an internal <a>unsafePerformIO</a> for calling
-- contexts that are already in the <a>IO</a> monad.
--
-- Returning any value containing IVar is still disallowed, as it can
-- compromise type safety.
runParIO :: Par a -> IO a
-- | An asynchronous version in which the main thread of control in a Par
-- computation can return while forked computations still run in the
-- background.
runParAsync :: Par a -> a
-- | Creates a new <tt>IVar</tt>
new :: Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value
newFull :: NFData a => a -> Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value (head-strict only)
newFull_ :: a -> Par (IVar a)
-- | Read the value in an <tt>IVar</tt>. The <a>get</a> operation can only
-- return when the value has been written by a prior or parallel
-- <tt>put</tt> to the same <tt>IVar</tt>.
get :: IVar a -> Par a
-- | Like <a>put</a>, but only head-strict rather than fully-strict.
put_ :: IVar a -> a -> Par ()
-- | Put a value into an <tt>IVar</tt>. Multiple <a>put</a>s to the same
-- <tt>IVar</tt> are not allowed, and result in a runtime error.
--
-- <a>put</a> fully evaluates its argument, which therefore must be an
-- instance of <a>NFData</a>. The idea is that this forces the work to
-- happen when we expect it, rather than being passed to the consumer of
-- the <tt>IVar</tt> and performed later, which often results in less
-- parallelism than expected.
--
-- Sometimes partial strictness is more appropriate: see <a>put_</a>.
put :: NFData a => IVar a -> a -> Par ()
pollIVar :: IVar a -> IO (Maybe a)
-- | Allows other parallel computations to progress. (should not be
-- necessary in most cases).
yield :: Par ()
instance GHC.Base.Functor Control.Monad.Par.Scheds.TraceInternal.Par
instance GHC.Base.Monad Control.Monad.Par.Scheds.TraceInternal.Par
instance GHC.Base.Applicative Control.Monad.Par.Scheds.TraceInternal.Par
instance GHC.Classes.Eq (Control.Monad.Par.Scheds.TraceInternal.IVar a)
instance Control.DeepSeq.NFData (Control.Monad.Par.Scheds.TraceInternal.IVar a)
-- | This is the scheduler described in the paper "A Monad for
-- Deterministic Parallelism". It is based on a lazy <tt>Trace</tt> data
-- structure that separates the scheduler from the <tt>Par</tt> monad
-- method implementations.
module Control.Monad.Par.Scheds.Trace
data Par a
-- | Run a parallel, deterministic computation and return its result.
--
-- Note: you must NOT return an IVar in the output of the parallel
-- computation. This is unfortunately not enforced, as it is with
-- <tt>runST</tt> or with newer libraries that export a Par monad, such
-- as <tt>lvish</tt>.
runPar :: Par a -> a
-- | A version that avoids an internal <a>unsafePerformIO</a> for calling
-- contexts that are already in the <a>IO</a> monad.
--
-- Returning any value containing IVar is still disallowed, as it can
-- compromise type safety.
runParIO :: Par a -> IO a
fork :: Par () -> Par ()
data IVar a
-- | Creates a new <tt>IVar</tt>
new :: Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value
newFull :: NFData a => a -> Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value (head-strict only)
newFull_ :: a -> Par (IVar a)
-- | Read the value in an <tt>IVar</tt>. The <a>get</a> operation can only
-- return when the value has been written by a prior or parallel
-- <tt>put</tt> to the same <tt>IVar</tt>.
get :: IVar a -> Par a
-- | Put a value into an <tt>IVar</tt>. Multiple <a>put</a>s to the same
-- <tt>IVar</tt> are not allowed, and result in a runtime error.
--
-- <a>put</a> fully evaluates its argument, which therefore must be an
-- instance of <a>NFData</a>. The idea is that this forces the work to
-- happen when we expect it, rather than being passed to the consumer of
-- the <tt>IVar</tt> and performed later, which often results in less
-- parallelism than expected.
--
-- Sometimes partial strictness is more appropriate: see <a>put_</a>.
put :: NFData a => IVar a -> a -> Par ()
-- | Like <a>put</a>, but only head-strict rather than fully-strict.
put_ :: IVar a -> a -> Par ()
spawn :: NFData a => Par a -> Par (IVar a)
spawn_ :: Par a -> Par (IVar a)
spawnP :: NFData a => a -> Par (IVar a)
instance Control.Monad.Par.Class.ParFuture Control.Monad.Par.Scheds.TraceInternal.IVar Control.Monad.Par.Scheds.TraceInternal.Par
instance Control.Monad.Par.Class.ParIVar Control.Monad.Par.Scheds.TraceInternal.IVar Control.Monad.Par.Scheds.TraceInternal.Par
-- | This scheduler uses sparks (par/pseq) directly, but only supplies the
-- <tt>Monad.Par.Class.ParFuture</tt> interface.
module Control.Monad.Par.Scheds.Sparks
data Par a
Done :: a -> Par a
data Future a
Future :: a -> Future a
runPar :: Par a -> a
get :: Future a -> Par a
spawn :: NFData a => Par a -> Par (Future a)
spawn_ :: Par a -> Par (Future a)
spawnP :: NFData a => a -> Par (Future a)
instance GHC.Base.Monad Control.Monad.Par.Scheds.Sparks.Par
instance Control.Monad.Par.Class.ParFuture Control.Monad.Par.Scheds.Sparks.Future Control.Monad.Par.Scheds.Sparks.Par
instance GHC.Base.Functor Control.Monad.Par.Scheds.Sparks.Par
instance GHC.Base.Applicative Control.Monad.Par.Scheds.Sparks.Par
-- | A scheduler for the Par monad based on directly performing IO actions
-- when Par methods are called (i.e. without using a lazy trace data
-- structure).
module Control.Monad.Par.Scheds.Direct
data Sched
Sched :: {-# UNPACK #-} !Int -> WSDeque (Par ()) -> HotVar GenIO -> Bool -> HotVar [Session] -> HotVar [MVar Bool] -> [Sched] -> HotVar (Set SessionID) -> HotVar SessionID -> Sched
[no] :: Sched -> {-# UNPACK #-} !Int
[workpool] :: Sched -> WSDeque (Par ())
[rng] :: Sched -> HotVar GenIO
[isMain] :: Sched -> Bool
[sessions] :: Sched -> HotVar [Session]
[idle] :: Sched -> HotVar [MVar Bool]
[scheds] :: Sched -> [Sched]
[activeSessions] :: Sched -> HotVar (Set SessionID)
[sessionCounter] :: Sched -> HotVar SessionID
data Par a
newtype IVar a
IVar :: (IORef (IVarContents a)) -> IVar a
data IVarContents a
Full :: a -> IVarContents a
Empty :: IVarContents a
Blocked :: [a -> IO ()] -> IVarContents a
runPar :: Par a -> a
runParIO :: Par a -> IO a
-- | Creates a new <tt>IVar</tt>
new :: Par (IVar a)
-- | Read the value in an <tt>IVar</tt>. The <a>get</a> operation can only
-- return when the value has been written by a prior or parallel
-- <tt>put</tt> to the same <tt>IVar</tt>.
get :: IVar a -> Par a
-- | <tt>put_</tt> is a version of <tt>put</tt> that is head-strict rather
-- than fully-strict. In this scheduler, puts immediately execute woken
-- work in the current thread.
put_ :: IVar a -> a -> Par ()
fork :: Par () -> Par ()
newFull :: NFData a => a -> Par (IVar a)
newFull_ :: a -> Par (IVar a)
put :: NFData a => IVar a -> a -> Par ()
spawn :: NFData a => Par a -> Par (IVar a)
spawn_ :: Par a -> Par (IVar a)
spawnP :: NFData a => a -> Par (IVar a)
spawn1_ :: (a -> Par b) -> a -> Par (IVar b)
instance Control.DeepSeq.NFData (Control.Monad.Par.Scheds.Direct.IVar a)
instance Control.Monad.Par.Class.ParFuture Control.Monad.Par.Scheds.Direct.IVar Control.Monad.Par.Scheds.DirectInternal.Par
instance Control.Monad.Par.Class.ParIVar Control.Monad.Par.Scheds.Direct.IVar Control.Monad.Par.Scheds.DirectInternal.Par
instance Control.Monad.Par.Unsafe.ParUnsafe Control.Monad.Par.Scheds.Direct.IVar Control.Monad.Par.Scheds.DirectInternal.Par
-- | This module is an alternative version of <a>Control.Monad.Par</a> in
-- which the <a>Par</a> type provides <a>IO</a> operations, by means of
-- <a>liftIO</a>. The price paid is that only <a>runParIO</a> is
-- available, not the pure <tt>runPar</tt>.
--
-- This module uses the same default scheduler as
-- <a>Control.Monad.Par</a>.
module Control.Monad.Par.IO
-- | A wrapper around an underlying Par type which allows IO.
data ParIO a
data IVar a
-- | A run method which allows actual IO to occur on top of the Par monad.
-- Of course this means that all the normal problems of parallel IO
-- computations are present, including nondeterminsm.
--
-- A simple example program:
--
-- <pre>
-- runParIO (liftIO $ putStrLn "hi" :: ParIO ())
-- </pre>
runParIO :: ParIO a -> IO a
instance Control.Monad.Par.Class.ParIVar Control.Monad.Par.Scheds.TraceInternal.IVar Control.Monad.Par.IO.ParIO
instance Control.Monad.Par.Class.ParFuture Control.Monad.Par.Scheds.TraceInternal.IVar Control.Monad.Par.IO.ParIO
instance GHC.Base.Monad Control.Monad.Par.IO.ParIO
instance GHC.Base.Applicative Control.Monad.Par.IO.ParIO
instance GHC.Base.Functor Control.Monad.Par.IO.ParIO
instance Control.Monad.IO.Class.MonadIO Control.Monad.Par.IO.ParIO
-- | The <tt>monad-par</tt> package provides a family of <tt>Par</tt>
-- monads, for speeding up pure computations using parallel processors.
-- (for a similar programming model for use with <tt>IO</tt>, see
-- <a>Control.Monad.Par.IO</a>.)
--
-- The result of a given <tt>Par</tt> computation is always the same -
-- i.e. it is deterministic, but the computation may be performed more
-- quickly if there are processors available to share the work.
--
-- For example, the following program fragment computes the values of
-- <tt>(f x)</tt> and <tt>(g x)</tt> in parallel, and returns a pair of
-- their results:
--
-- <pre>
-- runPar $ do
-- fx <- spawnP (f x) -- start evaluating (f x)
-- gx <- spawnP (g x) -- start evaluating (g x)
-- a <- get fx -- wait for fx
-- b <- get gx -- wait for gx
-- return (a,b) -- return results
-- </pre>
--
-- <tt>Par</tt> can be used for specifying pure parallel computations in
-- which the order of the computation is not known beforehand. The
-- programmer specifies how information flows from one part of the
-- computation to another, but not the order in which computations will
-- be evaluated at runtime. Information flow is described using
-- "variables" called <tt>IVar</tt>s, which support <a>put</a> and
-- <a>get</a> operations. For example, suppose you have a problem that
-- can be expressed as a network with four nodes, where <tt>b</tt> and
-- <tt>c</tt> require the value of <tt>a</tt>, and <tt>d</tt> requires
-- the value of <tt>b</tt> and <tt>c</tt>:
--
-- <pre>
-- a
-- / \
-- b c
-- \ /
-- d
-- </pre>
--
-- Then you could express this in the <tt>Par</tt> monad like this:
--
-- <pre>
-- runPar $ do
-- [a,b,c,d] <- sequence [new,new,new,new]
-- fork $ do x <- get a; put b (x+1)
-- fork $ do x <- get a; put c (x+2)
-- fork $ do x <- get b; y <- get c; put d (x+y)
-- fork $ do put a (3 :: Int)
-- get d
-- </pre>
--
-- The result of the above computation is always 9. The <a>get</a>
-- operation waits until its input is available; multiple <a>put</a>s to
-- the same <tt>IVar</tt> are not allowed, and result in a runtime error.
-- Values stored in <tt>IVar</tt>s are usually fully evaluated (although
-- there are ways provided to pass lazy values if necessary).
--
-- In the above example, <tt>b</tt> and <tt>c</tt> will be evaluated in
-- parallel. In practice the work involved at each node is too small here
-- to see the benefits of parallelism though: typically each node should
-- involve much more work. The granularity is completely under your
-- control - too small and the overhead of the <tt>Par</tt> monad will
-- outweigh any parallelism benefits, whereas if the nodes are too large
-- then there might not be enough parallelism to use all the available
-- processors.
--
-- Unlike <tt>Control.Parallel</tt>, in <tt>Control.Monad.Par</tt>
-- parallelism is not combined with laziness, so sharing and granularity
-- are completely under the control of the programmer. New units of
-- parallel work are only created by <tt>fork</tt> and a few other
-- combinators.
--
-- The default implementation is based on a work-stealing scheduler that
-- divides the work as evenly as possible between the available
-- processors at runtime. Other schedulers are available that are based
-- on different policies and have different performance characteristics.
-- To use one of these other schedulers, just import its module instead
-- of <a>Control.Monad.Par</a>:
--
-- <ul>
-- <li><a>Control.Monad.Par.Scheds.Trace</a></li>
-- <li><a>Control.Monad.Par.Scheds.Sparks</a></li>
-- </ul>
--
-- For more information on the programming model, please see these
-- sources:
--
-- <ul>
-- <li>The wiki/tutorial
-- (<a>http://www.haskell.org/haskellwiki/Par_Monad:_A_Parallelism_Tutorial</a>)</li>
-- <li>The original paper
-- (<a>http://www.cs.indiana.edu/~rrnewton/papers/haskell2011_monad-par.pdf</a>)</li>
-- <li>Tutorial slides
-- (<a>http://community.haskell.org/~simonmar/slides/CUFP.pdf</a>)</li>
-- <li>Other slides:
-- (<a>http://www.cs.ox.ac.uk/ralf.hinze/WG2.8/28/slides/simon.pdf</a>,
-- <a>http://www.cs.indiana.edu/~rrnewton/talks/2011_HaskellSymposium_ParMonad.pdf</a>)</li>
-- </ul>
module Control.Monad.Par
data Par a
-- | Run a parallel, deterministic computation and return its result.
--
-- Note: you must NOT return an IVar in the output of the parallel
-- computation. This is unfortunately not enforced, as it is with
-- <tt>runST</tt> or with newer libraries that export a Par monad, such
-- as <tt>lvish</tt>.
runPar :: Par a -> a
-- | A version that avoids an internal <a>unsafePerformIO</a> for calling
-- contexts that are already in the <a>IO</a> monad.
--
-- Returning any value containing IVar is still disallowed, as it can
-- compromise type safety.
runParIO :: Par a -> IO a
fork :: Par () -> Par ()
data IVar a
-- | Creates a new <tt>IVar</tt>
new :: Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value
newFull :: NFData a => a -> Par (IVar a)
-- | Creates a new <tt>IVar</tt> that contains a value (head-strict only)
newFull_ :: a -> Par (IVar a)
-- | Read the value in an <tt>IVar</tt>. The <a>get</a> operation can only
-- return when the value has been written by a prior or parallel
-- <tt>put</tt> to the same <tt>IVar</tt>.
get :: IVar a -> Par a
-- | Put a value into an <tt>IVar</tt>. Multiple <a>put</a>s to the same
-- <tt>IVar</tt> are not allowed, and result in a runtime error.
--
-- <a>put</a> fully evaluates its argument, which therefore must be an
-- instance of <a>NFData</a>. The idea is that this forces the work to
-- happen when we expect it, rather than being passed to the consumer of
-- the <tt>IVar</tt> and performed later, which often results in less
-- parallelism than expected.
--
-- Sometimes partial strictness is more appropriate: see <a>put_</a>.
put :: NFData a => IVar a -> a -> Par ()
-- | Like <a>put</a>, but only head-strict rather than fully-strict.
put_ :: IVar a -> a -> Par ()
spawn :: NFData a => Par a -> Par (IVar a)
spawn_ :: Par a -> Par (IVar a)
spawnP :: NFData a => a -> Par (IVar a)
-- | A class of types that can be fully evaluated.
class NFData a
|