@hackage / reflex

Higher-order Functional Reactive Programming

Latest0.9.4.0

About

Metadata

  • Last updated , by abrar
  • License BSD-3-Clause
  • Categories FRP

  • Maintained by: ryan.trinkle@gmail.com

  • Lottery factor: 5

Links

Installation

Tested Compilers

  1. 9.12.2
  2. 9.10.1
  3. 9.8.2
  4. 9.6.1
  5. 9.4.5
  6. 9.2.5
  7. 9.0.1
  8. 8.10.7
  9. 8.8.1
  10. 8.6.5
  11. 8.4.4

Package Flags

Use the -f option with cabal commands to enable flags

    debug-trace-events (off by default)

    Add instrumentation that outputs the stack trace of the definition of an event whenever it is subscribed to. Warning: It is very slow!

    fast-weak (off by default)

    Use the primitive implementation of FastWeak in GHCJS; note that this requires GHCJS to be built with FastWeak and FastWeakBag present in the RTS, which is not the default

    debug-propagation (off by default)

    Enable debugging of spider internals

    debug-cycles (off by default)

    Enable debugging of event cycles

    split-these (on by default)

    Use split these/semialign packages

Readme

Reflex

Haskell Hackage BSD3 License

Interactive programs without callbacks or side-effects. Functional Reactive Programming (FRP) uses composable events and time-varying values to describe interactive systems as pure functions. Just like other pure functional code, functional reactive code is easier to get right on the first try, maintain, and reuse.

Reflex is a fully-deterministic, higher-order Functional Reactive Programming interface and an engine that efficiently implements that interface.

Visit https://reflex-frp.org for more information, tutorials, documentation and examples.

Resources

Hacking

From the root of a Reflex Platform checkout, run ./scripts/hack-on haskell-overlays/reflex-packages/dep/reflex. This will check out the reflex source code into the haskell-overlays/reflex-packages/dep/reflex directory. You can then point that checkout at your fork, make changes, etc. Use the ./try-reflex or ./scripts/work-on scripts to start a shell in which you can test your changes.