J. S. Choi

> It doesn't need to _encourage_ tacit programming, merely enable it. The F# proposal achieves this by leaving open the opportunity to open up a lambda. I agree; this is...

> Yet the F# pipe proposal actually comes from... F#. Where it is extensively used in use code. So.... 🤔 Yes. F# itself gives several reasons to *avoid* point-free style...

> So minimal/F# style will ultimately never to get through TC39 based on what you have said above. @aadamsx: I would not yet say “definitely never”. But I would say...

Note for readers: There’s a lot of related talk about browser implementers’ concerns with F# pipes’ memory performance, starting from https://github.com/tc39/proposal-pipeline-operator/issues/215#issuecomment-922178037. I’m fine with that, since it feeds into frustration...

@micahscopes: Thanks for your well-reasoned comment. From what I know, the engine representatives’ performance concerns stem from the encouragement of widespread tacit programming, especially widespread curried functions, within hot paths,...

> > I plan to fight for F# pipes and PFA syntax later > > I need some clarification on this. If Hack pipes are adopted, what chances are there...

> > I know closure allocation is a concern when using such pipelines with lambdas, but tacit-style is not as prone to this, right? > > It's actually the opposite....

I’ve temporarily switched the topic token back from `^` to `#` (see #250). As per https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-926357211, I think my [change of the spec from `%` to `^`](https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-911851451) was premature, partially...

Starting on 2021-10-25, another formal Commitee plenary occurred. The [notes have now been published](https://github.com/tc39/notes/tree/master/meetings/2021-10). We have summarized these updates in #256. The pipe operator was not presented at this meeting,...

We had a [recent formal TC39 incubator call with publicly available notes in late November 2021][notes]. * We decided for now to switch to two-character topic tokens (`^^`, `@@`, or...