Hi Anthony,
Since short-circuiting sounds similar to a Subscriber cancelling its
Subscription, I believe it might be worthwhile to consider the Flow API.
If the argument would be a `Flow.Processor<T, R>`, then the
implementation would publish instances of T to it, subscribe to
receive instances of R, and be able to short-circuit by cancelling its
Subscription.
Disclaimer: I haven't actually prototyped this, but it makes sense at
first thought
Thanks for the suggestion. I refer to Paul's comments about why we don't
consider short-circuiting at the moment but might do so at a later point.
Cheers,
Julia
