Provide a higher arity version of merge(…) about swift-async-algorithms HOT 3 OPEN

@twittemb Is right here that this is something we ought to be able to do one variadic generics land. My position right now is to avoid adding sequence based APIs since they have a few downsides such as introducing an array allocation which could be avoided.

What I can recommend you for the time being is either of these two:

1. If merge is last transformation applied to your sequence chain then you can as @twittemb pointed out maybe use a task group and merge from there by just creating a child task for each upstream and calling next on the group repeatedly.
2. You could copy the code that is used for the implementation of merge and just extend it to whatever arity you need. This involves very minor changes and a bit of code duplication.

from swift-async-algorithms.

Hi

from what I know this is something that should arrive when generic variadics are available so we are not constrained to merging the same types of AsyncSequence.

Perhaps there are workarounds in your case. One that comes to my mind is (perhaps not the most efficient though):

Having a task group where you iterate over every channel you have (a task per channel) and send the elements to a single Channel. This “output” channel will act as a merging bus. You can then iterate over this single channel in another task.

from swift-async-algorithms.

Thanks to you both - that guidance and info is much appreciated.

I'll see if I can work out how to extend the existing code to support different arities in my local project.

I'll also go read up on the parameter packs pitch by Holly and Slava - I'm really excited by this bit of work!

from swift-async-algorithms.