- Group Reviewers
O2: Material Motion O6: Material Android platform reviewers Material Motion
- rMDMSTREAMSANDROID718cd799dd3a: Implement delayBy operator
Ah I think I just noticed a potential bug: if we connect, disconnect, and then connect again before the first connection's delayed event fired, it's possible that both connections will fire. We may need to correlate the active subscriptions with the delayed invocations in order to ensure that we're only receiving values for the most recent subscription.
ah, these stateful operators are harder to write than naively thought. There are 2 problems: