tfga

> What about >? Well, it's better than the current situation, I guess. But, still: in a language like dg, composition is probably used _way_ more than bit-shifting. I'd argue...

Hi, @0101! :wave: Thank you for your reply. > it will only save you adding `enumerate` in your pipe Not really: `enumerate` and `as_args`. At lease in my use case....

Not really. Every once in a while I find myself in a situation where I want to do a "foreach with index". The particular piece of code that prompted me...

> 1. The name - I think join might be too generic, because it could also be used to join different sequences together (think SQL JOIN), so maybe it should...

PS: Sorry for the huge delay in the reply. PPS: Thank you for the project. It changed my life. Seriously. When I first learned about it, I was like: "Where...

Somebody implemented this as a babel macro: https://github.com/Andarist/pipeline.macro

@jgonggrijp But then I'd have to duplicate this code in every project. To prevent that, isn't it the point of libraries like underscore?

@jgonggrijp Ok. Thanks for the replies.

@jgonggrijp No worries. Thank you for taking the time to explain this. I appreciate it.

The problem with backquotes is that they can't be nested. (Acctually, in bash there is a way to do this. But it's not pretty. > Command substitutions may be nested....