Pipeline Champions
2022-07-15
plaintext logs
prev next
source on github
12:25
<jschoi>

https://github.com/tc39/proposal-pipeline-operator/issues/217#issuecomment-1184910976


Edit: After it was clarified a more independent route of addressing my concerns can be feasible in the future, contrary to what I interpreted from strong stances expressed to me recently, I will bow out of these discussions indefinitely accordingly. My feedback regarding hack-style pipes impact on the functional-programming ecosystem can always be revisited whenever it next makes sense.

I wonder to what this is referring; it was a pretty sudden change.

12:27
<jschoi>
The closest thing I can think of is my mentioning in https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-1184950270 of the (small) possibility that Function.pipe and/or flow may be standardized, and that developers may use pipe/flow widely enough to warrant considering split-mix syntax again: x |>> f |>> g |>> h |> [^^].
16:23
<TabAtkins>
Me and Shu talked with them privately
17:59
<ljharb>
any chance long essay-like comments were discouraged in these conversations?
18:09
<TabAtkins>
Very explicitly by me, yes.
18:09
<TabAtkins>
Like, ended the conversation with "don't do this"