futures-signals
| Crates.io | futures-signals |
| lib.rs | futures-signals |
| version | 0.3.34 |
| source | src |
| created_at | 2018-03-18 11:05:40.530983 |
| updated_at | 2024-07-26 03:10:50.698107 |
| description | Zero cost FRP signals using the futures crate |
| homepage | https://github.com/Pauan/rust-signals |
| repository | https://github.com/Pauan/rust-signals |
| max_upload_size | |
| id | 56242 |
| size | 392,946 |
(Pauan)
documentation
README
This is a Rust crate that provides zero-cost FRP 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!
The best way to learn more is to read the tutorial.