Or is this simply a limitation of combinators because closures can't return to the top-level scope, whereas blocks *can*. Ugh, my intuition is telling me it's exactly this, and I really don't like it. Or well, it could be done, but it would likely require buffering. Which is :(
-
-
Show this thread
-
I'm mostly just hoping I've missed something, and someone here can spot what I've missed.
Show this thread -
Oops, I should've clarified: I don't mean "all errors". I mean: "keep forwarding input into a new stream, but exit on the first error". Also without buffering.
Show this thread -
New conversation -
-
-
Sure, you can do anything with a fold that you could do with a loop, but it feels iffy to swallow errors in the return type.
-
Oh, so I want to *handle* errors, not make them go away. E.g. return on the first error case, or continue going on. I guess the assumption here is that the source is not guaranteed to be finite, so returning on the first error seems like the most sane approach.
- 6 more replies
New conversation -
-
-
Do you want to _handle_ all errors or stop on first error?
-
Stop on the first error.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
