proposal-pipeline-operator

Proposal from 2015 to add pipes to JS: https://github.com/tc39/proposal-pipeline-operator

Just an FYI to folks, there has been a proposal to add pipes to JavaScript for a few years: https://github.com/tc39/proposal-pipeline-operator

If you read all the text, it seems like the entire repo is intended to be a satire on https://github.com/tc39/proposal-pipeline-operator.

Which is basically what the proposal is https://github.com/tc39/proposal-pipeline-operator#this-prop...

There is a proposal to add the pipeline operator |> to the standard that works similar to what you have here. https://github.com/tc39/proposal-pipeline-operator

Its all a problem of formatting, for me this is simple to read. const { status } = await send( capitalize(greeting) + "!" ) But i would not concat things in a method call, bad style. const message = capitalize(greeting) + "!" const { status } = await send(message) The example from the page is a little bit too simple. With complex operations a pipe-method would make more sense. But i will wait for the native pipeline-operator <https://github.com/tc39/proposal-pipeline-operator> instead using now a function.

Thing is: you don't read it easily. It's basically a custom DSL bolted on top of Javascript that hides actual functionality beneath an Everest of abstractions. That is, it's a yet another library trying to force Haskell/Haskellisms into Javascript and claiming with no proof other than emotions that it's so much better and more readable than something. Here's an actual readable version of that: try{ return getTurnPromptMessages(state, action) .map(mkCCRequestFromMessages) .map(addSchemaToRequest) .map(handleChatCompletion) .map(extractFirstCompletionChoice) .map(extractChatCompletionMessage) .map(decodeSchema) .map(detectLocation); } catch (e) { mkMessageError(e); } It can be further simplified. For example, you don't need two separate functions to extract the

Both are active tc39 proposals :) https://github.com/tc39/proposal-pipeline-operator - Stage 2 https://github.com/tc39/proposal-pattern-matching - Stage 1 Hopefully we get both in the next couple of years.

We often add promising TC39 proposals into Civet so people can experiment without waiting. We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others. Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)

and kudos also belong to the people whove been heavily championing and bikeshedding the proposal on behalf of the rest of us for the last 8 years - which i just discovered is really nicely documented in the repo: https://github.com/tc39/proposal-pipeline-operator/blob/main... there's usually a ton of nuance behind the syntax considerations and i usually find that the people on tc39 care way more than i do about the things i never think about until its too late. peeking into their discussions is often very enlightening... and a reminder of how hard it is to do language design by committee and at scale.

The proposal is not finished yet (and might never been). Pessimism aside, there is a whole issue on why it was decided on following up with Hack's implementation [1]. You can always give your input on such decisions, the % token is still being "bikeshedded"[2] (is that a word?), and there's still a possibility of making follow-ups proposals that could implement some F#-esque implementation [1]: https://github.com/tc39/proposal-pipeline-operator/issues/22... [2]: https://github.com/tc39/proposal-pipeline-operator/issues/91

Pipes and pattern matching have been proposed to JS. https://github.com/tc39/proposal-pipeline-operator https://github.com/tc39/proposal-pattern-matching