Feature request: Multi-arg flatMap

[jessekelly881]

It's very common (at least in the code I write) to have multiple Effect.flatMap chains. It would be very useful to extend the flatMap function to help reduce boilerplate.

Effect.flatMap( // Effect<..., C>
    Effect<..., A>
    (a: A) => Effect<..., B>,
    (a: B) => Effect<..., C>,
    // etc...
)

[fubhy]

Overloading an api with alternative syntax for the same things should generally be avoided unless there's a real benefit to it. In this case, I'm doubtful that adding built-in pipe-like behavior to flatMap (or any other operator) would be beneficial. In my opinion, this'd negatively impact readability and composability.

Effect.flatMap( // Effect<..., C>
    Effect<..., A>
    (a: A) => Effect<..., B>,
    (a: B) => Effect<..., C>,
    // etc...
)

vs.

pipe(
  // ...
  Effect.flatMap(...),
  Effect.flatMap(...),
  Effect.flatMap(...),
  // etc...
)

I personally prefer the latter.

[mikearnaldi]

I feel like adding this only to flatMap would be awkward and adding it everywhere counter-productive, it is also a good use case for generators so the motivation isn't too strong for it to be included in the library

[jessekelly881]

Makes sense. Ok. I'll close this for now.