TODO

[polytypic]

Next:

• Support for Unix.wait and related functionality in Picos_stdio
• Structured concurrency library/sample/primitives
• A randomized scheduler (for testing)
• Make sure time limited QCheck STM tests will use different seeds
• Make the specification related to when the scheduler must propagate cancelation to fiber clear (i.e. if computation of the fiber has been canceled e.g. prior (happened before) to spawn then must the scheduler propagate cancelation or not?)
• What, exactly, should e.g. Trigger.await do when the computation of the fiber has returned (not canceled)?
• Carefully consider, document, and fix handling of asynchronous exceptions
  • How to best deal with Ctrl-C?
• Elaborate on core library contracts
  • Elaborate on requirements for scheduler on effects (Elaborate on contracts #128)
  • Elaborate on pre- and postconditions of key operations
• Picos_select automatic and explicit shutdown and full reconfiguration
• Scheduler concept, i.e. ability to spawn to specified scheduler possibly on another thread/domain
• io_uring, poll, possibly iocp, ... based async IO libraries
• Split picos into two packages

Soon:

• Lwt interop
  • Lwt based scheduler
  • Use notifications in Picos_lwt_unix
  • Bridge to call Lwt from any Picos scheduler
• Async interop
• Higher-level unstructured concurrency library

Eventually:

• Sample JavaScript scheduler
• Synchronous channel