Microsoft rx
I myself created the project by combining the Kernel , Interfaces , Linq, and PlatformServices from Rx codeplex .
There you go:
https://github.com/stampsy/rx-monotouch
It works great with reference types, and even more so with value types (see below).
Unfortunately, it does not compile due to errors 8329 and 9087 . Now it compiles.
mono-reactive
I also used mono-reactive and it worked very well for me. While Microsoft's implementation seems more concise and reliable, monoreactivity is smaller and easier to fix when it really is needed.
You can try both and see what works best for you.
Happy observation!
Mitigating Failures
In both environments, I often encountered crashes caused by AOT device restrictions. Rolf Hamarin told me that you can often work with most AOT restrictions on without using value types like Rx.
For example, the IObservable<bool> extensions are likely to get corrupted on the device, and this will be the IObservable<long> , but reference types should work fine with most methods.
In my version of Rx, I added an IntervalSafe method that returns Unit (which I changed as a reference type, not a structure) instead of long and therefore does not cause dozens of crashes throughout the code base.
Some Rx methods still crash, but it's pretty easy to fix these crashes .
See Throttle fix with Costo or my Buffer fix for help.
I am pleased to combine traction requests that will appeal to other Rx methods and their overloads.
Dan abramov
source share