ES7 Proposal: The Pipeline Operator
github.com
ES7 Proposal: The Pipeline Operator
1–10 of 78 posts
Re: ES7 Proposal: The Pipeline Operator
#2I liked this feature in LiveScript rather much.
Especially that it worked in both directions.
my-list = filter Re: ES7 Proposal: The Pipeline Operator
#3Doesn't LiveScript already have it ?
Re: ES7 Proposal: The Pipeline Operator
#4Can we just put more focus on sweet.js so we can do this kind of in a library with standard build tooling? http://sweetjs.org/
There's a lot more operators than |> that you would want. Clojure commonly uses ->, ->>, as->, etc. It should be done in a library if it is done at all.
Also, going full-on functional in javascript is going to end badly, javascript simply wasn't designed for it. If you go down this path in real projects, sooner or later you inevitably end up at clojurescript or whatever other real FP language suits.
Re: ES7 Proposal: The Pipeline Operator
#5I like this a lot. It's similar to the proposed function bind syntax[1], but a bit more friendly to not-`this`-related use:
function bindMap(fn) { return this.map(fn) }
[ 1, 2, 3 ]::bindMap(n => n + 1)
// standalone use: bindMap.call(arr, fn)
function pipelineMap(fn) { return arr => arr.map(fn) }
[ 1, 2, 3 ] |> pipelineMap(n => n + 1)
// standalone use: pipelineMap(fn)(arr)
Presumably, at most one of these proposals will make it in :)
Re: ES7 Proposal: The Pipeline Operator
#6In concatenative languages, this style of composition is the norm, and it does indeed work well for many tasks:
Re: ES7 Proposal: The Pipeline Operator
#7I feel like that just confuses things for no good reason. It's no fewer characters than parens but provides as I see it less clarity.
Re: ES7 Proposal: The Pipeline Operator
#8What's so painful about just doing `exclaim(capitalize(doubleSay("hello")));`? Why introduce needless syntactic sugar that'll only confuse people about how UNIX pipes work?
Re: ES7 Proposal: The Pipeline Operator
#9Please no.
Javascript's beauty lies in its versatile simplicity. Can we just leave these sorts of things to systems programming languages like C++? I came to javascript because of its lack of cruft, but if libraries start adopting this then I'll be forced to put it in my code as well. If that happens then I'll probably leave for nim or clojure, though that's not preferable.
Re: ES7 Proposal: The Pipeline Operator
#10As an F# user, I like this a lot, very similar although it can confuse people. It's very much a trait of functional programming and it's easy to read once you get the hang of it :)