Search Results for "effects"

...The core of Koka consists of a small set of well-studied language features, like first-class functions, a polymorphic type- and effect system, algebraic data types, and effect handlers. Each of these is composable and avoid the addition of “special” extensions by being as general as possible. Koka tracks the (side) effects of every function in its type, where pure and effectful computations are distinguished. The precise effect typing gives Koka rock-solid semantics backed by well-studied category theory, which makes Koka particularly easy to reason about for both humans and compilers. Effect handlers let you define advanced control abstractions, like exceptions, async/await, or probabilistic programs, as a user library in a typed and composable way. ...

This repository accompanies a comprehensive guide to building large, maintainable Haskell systems, focusing on architecture, modularity, and practical design techniques. It presents patterns for separating pure domain logic from side effects, organizing code into layers and components that can be tested in isolation. Readers encounter multiple styles—MTL/typeclass constraints, tagless-final encodings, free and freer monads, ReaderT-style application environments—and learn when to apply each. The examples emphasize explicit boundaries for infrastructure concerns such as persistence, logging, configuration, and external services to keep business logic clean. ...

...It features a virtual-dom, recursive diffing / patching algorithm, attribute and property normalization, event delegation, event batching, SVG, Server-sent events, Websockets, type-safe servant-style routing and an extensible Subscription-based subsystem. Inspired by Elm, Redux and Bobril. Miso is pure by default, but side effects (like XHR) can be introduced into the system via the Effect data type. Miso makes heavy use of the GHCJS FFI and therefore has minimal dependencies. Miso can be considered a shallow embedded domain-specific language for modern web programming.

Reflex apps automatically react to changing data. This keeps every interaction current, accurately representing the relationship between your data and the real world. Reflex components are modular and reusable. If your requirements change, your app can quickly and easily be reworked. The modularity of Reflex lets you iterate quickly, without wasting code. Reflex has been built to seamlessly support interfaces on desktop, mobile, web, and other platforms, all in Haskell. Regardless of your...

...Programs are composed by chaining small words that transform a typed stack, and the compiler uses type inference to ensure compositions are valid. The language explores disciplined handling of side effects, aiming to separate pure transformations from operations that perform I/O or mutate state. Its design encourages small, reusable building blocks that compose cleanly, while still permitting low-level control where performance matters. The implementation targets efficient compiled code and investigates how advanced type systems can improve reliability in a stack-based language. ...

Polysemy is a high-performance, zero-boilerplate effect system for Haskell, designed to simplify the handling of side effects in functional programs. Unlike traditional monad transformer stacks, Polysemy uses a modern approach based on freer monads and interpreters, allowing developers to define, compose, and interpret effects in a more modular and testable way. It aims to offer both flexibility and performance without sacrificing type safety or expressiveness.

Reanimate is a Haskell-based animation library for programmatically creating high-quality vector animations. It provides declarative functionality for composing SVG-based animations and integrates with tools like LaTeX, FFmpeg, Inkscape, Blender, and more to deliver rich, animated content for educational and mathematical visualizations. Reanimate aims at being a batteries-included way of gluing together different technologies: SVG as a universal image format, LaTeX for typesetting, ffmpeg...

... - STM Memory is easy to share over all the threads, easy to keep apart and when needed to switch between the both. - Strict typesystem You can't send the wrong information to a function, and you can not possibly use it in a way not intended - No side-effects A function can't do anything else then what you want it to do. You provide a value, it returns a value. No fishy business. Read the Readme.txt for more information on how to compile.