another-rxrust
why new implementation?
rxRust is a Rust language implementation of ReactiveX, but it is not suitable for complex combinations of observable.
For those who use ReactiveX in other languages such as rxjs(TypeScript) or rxcpp, rxRust is a very difficult library.
Therefore, I created another-rxrust, thinking that I needed a library that allows observable to be connected in the same way as other platforms, and that ReactiveX can be enjoyed in Rust.
In addition, ReactiveX may not be the best solution if the purpose is to parallelize heavy processing and speed it up. However, ReactiveX is one answer for complex combinations of non-blocking I/O and error handling.
Implementation policy
- It is assumed that the values and functions that can be emitted may be shared between threads.
- Value to emit should be
Clone + Send + Synconly. - Use
moveto emit values as much as possible. - Functions should be
Fn() + Send + Synconly. - Errors are type-erased using
std::any.- Thus requiring a
'staticlifetime. - You can use
anyhow.
- Thus requiring a
- Prioritize flexibility over memory efficiency and execution speed.
Implementation status
Installation
or
[]
= {}
If you want to use it on the web, set it as follows.
[]
= {=["web"]}
Samples
from_iter, map, zip
use *;
use ;
// [console-results]
// next - [0, 10, 20]
// next - [1, 11, 21]
// next - [2, 12, 22]
// next - [3, 13, 23]
// next - [4, 14, 24]
// next - [5, 15, 25]
// next - [6, 16, 26]
// next - [7, 17, 27]
// next - [8, 18, 28]
// next - [9, 19, 29]
// complete
subject, scheduler, take, sample
use *;
use ;
use ;
// [console-results (Depends on execution environment)]
// next - 3
// next - 8
// next - 13
// complete
just, error, emptry, never, flat_map...
use *;
use ;
// [console-results]
// next 2
// next 103
// next 203
// next resume "some error" 100
// next resume "some error" 200
// complete