> Hey Larry,
> On Sat, Jul 17, 2021 at 6:00 PM Larry Garfield <email@example.com>
>> Hi Marco. Thank you for your explanation, even if I naturally disagree.
>> Out of curiosity, what sort of additional
>> power/capability/flexibility/etc. would, in your mind, justify pipe or
>> similar being a native feature? PHP has a *ton* of native features that
>> *could* be done in user space, or are simply syntax sugar, but still
>> popular and useful as native syntax. What is your heuristic for that?
>> (The fact that there are 3-4 user space implementations of pipe-like
>> behavior, all incompatible, is one of the reasons why I think
>> it into a common core syntax *is* a good idea, though I know others
> I think the pipe operator as a **custom** operator made sense when we had
> the entire discussion around placeholder parameters (`$$`) to be used in
> the pipeline.
> As a plain "chain of functions with one input parameter and one output", it
> makes little sense to have it as a custom construct, as it only adds
> complexity to the AST.
That is the idiomatic implementation, though. Hacklang is the odd man
out with $$.