mapFunc (temporary name)

pipeMulti carries on multiple iterable transformations in parallel:

const iter1 = range(10)
const iter2 = range(10)
const even = filter((n) => n % 2 === 0)
const square = map((n) => n * n)
const [evenIter1, squareIter2] = pipeMulti([even, square], [iter1, iter2])

It can be used in pipelines, leveraging fork (or tee)

const [evenIter1, squareIter2] = pipe(
  range(10),
  fork(2), // this fork return 2 items
  pipeMulti([even, square])
)

Given that often times you precede pipeMulti with “fork”, it would be nice if pipeMulti can fork automatically whenever the second argument is an iterable instead of an array.

const iter = range(10)
const even = filter((n) => n % 2 === 0)
const square = map((n) => n * n)
const [evenIter1, squareIter2] = pipeMulti([even, square], iter)

That become:

const [evenIter1, squareIter2] = pipe(
  range(10),
  pipeMulti([even, square]) // it implicitly fork(2)
)

[KSXGitHub]

I don’t think the name should reflect the implementation but rather its use.

When I compared the function to map, I didn’t think of its implementation, but rather, its “shape”.

Anyway, whatever is the name, it should not contain “pipe”, because it doesn’t look like pipe in the slightest.

[sithmel]

This will be pretty much the implementation @KSXGitHub 👍

I don’t think the name should reflect the implementation but rather its use. I’ll run the idea with my colleagues (English is not my mother tongue either)