Sorry. I still cannot grip the point on how to pass errors or maybe
exceptions down the stream in a neat way without stopping the stream.
Swallowing errors (including programming faults) wouldn't be an option
since its required for nearly all circumstances to send an appropriate
reply to the
I see.
So no happy path programming while not loosing the error case with reactive
streams? This is a quite a bit disillusioning. Should be mentioned in all
those shiny reactive stream presentations ;-)
Is there some per stream exception handling mechanism instead which would
materialize with
Hi Leslie,
On Tuesday, July 14, 2015 at 1:38:02 PM UTC+2, leslie...@googlemail.com
wrote:
When programming with functions this kind of issue is solved quite
elegantly by using a for comprehension:
Not a solution but a comment. In a for comprehension with usual types
Am Dienstag, 14. Juli 2015 15:42:33 UTC+2 schrieb √:
Hi Leslie,
On Tue, Jul 14, 2015 at 3:34 PM, leslie...@googlemail.com javascript:
wrote:
I see.
So no happy path programming while not loosing the error case with
reactive streams? This is a quite a bit disillusioning. Should be
On Tue, Jul 14, 2015 at 4:51 PM, leslie.le...@googlemail.com wrote:
Am Dienstag, 14. Juli 2015 15:42:33 UTC+2 schrieb √:
Hi Leslie,
On Tue, Jul 14, 2015 at 3:34 PM, leslie...@googlemail.com wrote:
I see.
So no happy path programming while not loosing the error case with
reactive
