The ramus package

[Tags:benchmark, library, mit, test]

Ramus is a direct port of purescript-signal into Haskell, offering the Elm signal system for Haskell.

[Skip to Readme]


Versions 0.0.1, 0.1.0, 0.1.1, 0.1.2
Dependencies base (==4.*) [details]
License MIT
Maintainer Nikita Tchayka
Stability Unknown
Category Other
Home page
Bug tracker
Source repository head: git clone
Uploaded Tue Feb 7 21:23:26 UTC 2017 by NickSeagull
Distributions NixOS:0.1.2, Stackage:0.1.2, Tumbleweed:0.1.2
Downloads 55 total (15 in the last 30 days)
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]




Maintainer's Corner

For package maintainers and hackage trustees

Readme for ramus

Readme for ramus-0.1.2


Ramus is a lightweight FRP-like library heavily inspired by the Elm Signal implementation, in fact, it's a direct port of the purescript-signal library, in Haskell. Where possible and sensible, it tries to maintain API equivalence with Elm. See the Elm documentation for details on usage and principles.

Haskell Usage Patterns

Haskell depends on IO to manage side effects, where Elm's runtime generally manages them for you. ramus provides the Signal.runSignal function for running effectful signals.

module Main where

import Signal

hello :: Signal String
hello = constant "Hello Joe!"

helloEffect :: Signal (IO ())
helloEffect = hello ~> print

main :: IO ()
main = runSignal helloEffect

This simple example takes a constant signal which contains the string "Hello Joe!" and maps it over the print function, which has the type (Show a) => a -> IO(), thus taking the String content of the signal and turning it into an effect which logs the provided string to the user's console. This gives us a Signal (IO ()). We use runSignal to take the signal of effects and run each effect in turn—in our case, just the one effect which prints "Hello Joe!" to the console.

API Documentation

Usage Examples

  • TODO