package picos

You can search for identifiers within the package.

in-package search v0.2.0

picos
- Picos
  - Computation
  - Fiber
    
    FLS
    
    Maybe
  - Handler
  - Trigger
picos.domain
- Picos_domain
  - DLS
picos.exn_bt
- Picos_exn_bt
picos.fd
- Picos_fd
  - Resource
picos.fifos
- Picos_fifos
picos.htbl
- Picos_htbl
picos.lwt
- Picos_lwt
  - System
picos.lwt_unix
- Picos_lwt_unix
picos.mpscq
- Picos_mpscq
picos.randos
- Picos_randos
picos.rc
- Picos_rc
  - Make
    
    Resource
  - Resource
  - S
    
    Resource
picos.select
- Picos_select
  - Intr
picos.stdio
- Picos_stdio
  - Unix
    
    LargeFile
picos.structured
- Picos_structured
  - Bundle
  - Control
  - Finally
  - Promise
  - Run
picos.sync
- Picos_sync
  - Condition
  - Lazy
  - Mutex
picos.thread
- Picos_thread
  - TLS
picos.threaded
- Picos_threaded

Legend:
Library
Module
Module type
Parameter
Class
Class type

Randomized multi-threaded effects based Picos compatible scheduler for OCaml 5.

ℹ️ This scheduler implementation is specifically intended for testing libraries implemented in Picos.

Picos is an interface that allows schedulers to make scheduling decisions freely. After each effect this scheduler picks the next fiber to run randomly from the collection of ready fibers. This can help to discover bugs in programs implemented in Picos that make invalid scheduling assumptions.

type t

Represents a shared context for randomized runners.

val context : unit -> t

context () creates a new context for randomized runners. The context should be consumed by a call of run ~context ....

val runner_on_this_thread : t -> unit

runner_on_this_thread context starts a runner on the current thread to run fibers on the context. The runner returns when run ~context ... returns.

val run : ?context:t -> ?forbid:bool -> (unit -> 'a) -> 'a

run main runs the main thunk with the scheduler. Returns after main and all of the fibers spawned by main have returned.

The optional context argument specifies a context in which to run the main thunk. If unspecified, a new context is automatically created and the scheduler will be single-threaded. By creating a context, spawning concurrent or parallel runners on to the context, and then explicitly passing the context to run ~context ... one can create a multi-threaded scheduler. Only a single call of run per context is allowed.

The optional forbid argument defaults to false and determines whether propagation of cancelation is initially allowed.