perhaps model errors as data too? Rather than either returning 5 or crashing, you could return {:ok 5} or {:error "DivideBy0Error"}.

yeah @U3X7174KS - that's roughly my next approach - the only difficulty is that i'll need to add another layer of stream/chan to unwrap and then maybe close the downstream stream/chan... but i can't currently see any alternative

modeling failure right in a concurrent context is a challenge! I don't feel like I have a good answer for that. But I often feel like starting from "it's just data" pushes me in the right direction.

it's just data™

love the name

Did I ever try and sell you on clip? I built the manifold executor with you in mind.

no @U09LZR36F - i don't remember any sales pitch!

It's async, manifold, cljs, edn, compatible. All the things. It should support everything you might need ;)

I definitely built it with you in mind based on conversations we must have had many years ago now

where's the repo @U09LZR36F? can't find it on your gh...

Juxt repo

https://github.com/juxt/clip

ohhhhh, yes you did sell me on that! i didn't remember it was called clip - but i was actually looking for it a few weeks ago, 'cos it would allow me to delete some code

well that's good - thanks @U09LZR36F - i can delete that code now 😁 (it's actually still in the promisespromises repo, commented out... i was going to rewrite it to ditch the monad transformer in favor of an interceptor chain)

I'm glad to have turned up at just the right moment to help 🙂.

@U0509NKGK i am rubbish at project naming - this might be the single instance ever where i've come up with a good name!