Lecture, Tutorial, Product Demonstration
Effective Programming: Adding an Effect System to OCaml
- Plans to integrate an algebraic effects system to define unsupported side-effect operations, enabling concurrency features like thread forking and yielding without native language support.
- Aims to implement handlers for native state and I/O, region annotations for local state, and specific "freezing" mechanisms to return mutable state as immutable values.
- Introduces syntactic sugar via double-headed arrows to explicitly mark pure functions while retaining original signatures for impure ones, alongside "withFile" functionality to restrict file access to local regions.
- Targets future investigation into multi-handlers for concurrent computation execution and expects the standard library conversion to require roughly equal splits between logic fixes and type annotation updates.
- Anticipates that the system will distinguish between "throw" (resumable) and "raise" (non-resumable) exceptions to optimize performance while reserving "raise" for fatal errors.
- Expects polymorphic comparisons involving mutable state to be marked as side-effecting operations and anticipates the system will be largely backwards compatible with minimal syntax changes to existing code.
- Envisions a standard library written using only four distinct arrow types to represent all purity and effect combinations, with the definition of asynchronous operations kept abstract in the interface.
- Warns that implementing native references as algebraic effects via generic store handlers may be significantly less efficient than direct memory settings.
- Foresees that region-based typing will prevent references from different local handlers from crossing over, thereby avoiding runtime errors and allowing functions using local state to be correctly inferred as pure.
- Predicts that tracking effects in the type system will prevent unhandled effect errors typically associated with traditional exception handling.