#signal #reactive #frp #futures

futures-signals

Zero cost FRP signals using the futures crate

13 releases

✓ Uses Rust 2018 edition

new 0.3.6 Jun 10, 2019
0.3.5 Apr 27, 2019
0.3.4 Feb 24, 2019
0.3.2 Jan 30, 2019
0.1.0 Mar 18, 2018

#67 in Asynchronous

Download history 21/week @ 2019-02-23 27/week @ 2019-03-02 12/week @ 2019-03-09 16/week @ 2019-03-16 82/week @ 2019-03-23 1/week @ 2019-03-30 12/week @ 2019-04-06 4/week @ 2019-04-13 2/week @ 2019-04-20 30/week @ 2019-04-27 15/week @ 2019-05-04 26/week @ 2019-05-11 40/week @ 2019-05-18 16/week @ 2019-05-25 26/week @ 2019-06-01

94 downloads per month
Used in 2 crates

MIT license

186KB
3.5K SLoC

This is a Rust crate that provides zero-cost Signals which are built on top of the futures crate.

Hold on, zero-cost? Yup, that's right: if you don't use a feature you don't pay any performance cost, and the features that you do use are as fast as possible. Signals are very efficient.

What is a Signal? It is a value that changes over time, and you can be efficiently notified whenever its value changes.

This is useful in many situations:

  • You can automatically serialize your program's state to a database whenever it changes.

  • You can automatically send a message to the server whenever the client's state changes, or vice versa. This can be used to automatically, efficiently, and conveniently keep the client and server's state in sync.

  • A game engine can use Signals to automatically update the game's state whenever something changes.

  • You can easily represent continuous input (such as the current temperature, or the current time) as a Signal.

  • If you create a GUI, you can use Signals to automatically update the GUI whenever your state changes, ensuring that your state and the GUI are always in sync.

  • You can use dominator to create web apps and automatically keep them in sync with your program's state.

  • And many more situations!

Dependencies

~1MB
~20K SLoC