Markus Thömmes
Markus Thömmes
@johanandren sweet! I'd gladly take the task to code it up and everything. Which arities do you think make sense to implement? Only 2 for a start?
Investigated a bit: 1. It is possible to build any number of combinations using just `combineMat(2)` by just applying it multiple times to the combined sinks again. Return type will...
`GraphDSL` certainly is, in general, the answer, definitely. One caveat here was though, I had to understand the `GraphDSL.create` bits of importing shapes and combining their materialized values. Wasn't too...
Sounds good to me @johanandren :)
@tonicsoft With #24102 you'd only be able to get a list of materialized values of exactly one type, does it? This proposal is more about returning the distinct value (+...
@ktoso Fine for me as well (although I feel like both is worth having). A few questions: ### First: Would `recoverWithRetries(0, case _ => Source.empty)` work in theory? ### Second:...
> If you care about keeping errors in stream order, then they must be elements. Stream failure is like an "OOM", it's not something you should continiously do and recover...
> I'm not sure it's great to add overloads with boolean parameter to all of those compared to composing with .recoverWith or perhaps add a new recoverWithCompleted. You typically place...
Ha, that's a fair point! 🎉 One last question regarding "catching the error signal" (I'm not super deep into reactive streams, please bear with me): Will the error signal be...
Looking into adding `recoverTermination` now.