Crates.io | rxrust |
lib.rs | rxrust |
version | |
source | src |
created_at | 2019-07-31 15:01:17.138027 |
updated_at | 2024-10-25 15:45:41.284393 |
description | A Rust implementation of Reactive Extensions. |
homepage | https://github.com/rxRust/rxRust |
repository | https://github.com/rxRust/rxRust |
max_upload_size | |
id | 153205 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Add this to your Cargo.toml:
[dependencies]
rxrust = "1.0.0-beta.0"
use rxrust:: prelude::*;
let mut numbers = observable::from_iter(0..10);
// create an even stream by filter
let even = numbers.clone().filter(|v| v % 2 == 0);
// create an odd stream by filter
let odd = numbers.clone().filter(|v| v % 2 != 0);
// merge odd and even stream again
even.merge(odd).subscribe(|v| print!("{} ", v, ));
// "0 2 4 6 8 1 3 5 7 9" will be printed.
In rxrust
almost all extensions consume the upstream. So when you try to subscribe a stream twice, the compiler will complain.
# use rxrust::prelude::*;
let o = observable::from_iter(0..10);
o.subscribe(|_| println!("consume in first"));
o.subscribe(|_| println!("consume in second"));
In this case, we must clone the stream.
# use rxrust::prelude::*;
let o = observable::from_iter(0..10);
o.clone().subscribe(|_| println!("consume in first"));
o.clone().subscribe(|_| println!("consume in second"));
If you want to share the same observable, you can use Subject
.
rxrust
use the runtime of the Future
as the scheduler, LocalPool
and ThreadPool
in futures::executor
can be used as schedulers directly, and tokio::runtime::Runtime
is also supported, but need to enable the feature futures-scheduler
. Across Scheduler
to implement custom Scheduler
.
Some Observable Ops (such as delay
, and debounce
) need the ability to delay, futures-time supports this ability when set with the timer
feature, but you can also customize it by setting the new_timer function to NEW_TIMER_FN variant and removing the timer
feature.
use rxrust::prelude::*;
// `FuturesThreadPoolScheduler` is the alias of `futures::executor::ThreadPool`.
let threads_scheduler = FuturesThreadPoolScheduler::new().unwrap();
observable::from_iter(0..10)
.subscribe_on(threads_scheduler.clone())
.map(|v| v*2)
.observe_on_threads(threads_scheduler)
.subscribe(|v| println!("{},", v));
Also, rxrust
supports WebAssembly by enabling the feature wasm-scheduler
and using the crate wasm-bindgen
. A simple example is here.
Just use observable::from_future
to convert a Future
to an observable sequence.
use rxrust::prelude::*;
let mut scheduler_pool = FuturesLocalSchedulerPool::new();
observable::from_future(std::future::ready(1), scheduler_pool.spawner())
.subscribe(move |v| println!("subscribed with {}", v));
// Wait `task` finish.
scheduler_pool.run();
A from_future_result
function is also provided to propagate errors from `Future``.
See missing features to know what rxRust does not have yet.
We are looking for contributors! Feel free to open issues for asking questions, suggesting features or other things!
Help and contributions can be any of the following:
you can enable the default timer by timer
feature, or set a timer across function new_timer_fn