未加星标

The JavaScript Pipeline Operator

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二05 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

There is a very early proposal for the next version of javascript (aka ESNext proposal) which I’m really eager to see making it through.

I’m talking about the pipeline operator “|>”.

Immediately, all the guys coming from the functional world know what I’m talking about. Pipeline operator has been for some time in Elm , Elixir , and many other functional languages. Unix users should also feel familiar vibes .

So what is a pipeline?

Well, the basic idea is very straightforward. But let’s consider a problem first.

THE problem

Very often (or is always?) the code we write is about a series of transformation. We take some piece of data and consequentially transform it to get what we need.

Let’s look at the example you will probably never see in real life :wink: We’ll pretend we have the infamous lodashlibrary at our disposition

function maxSalary(departments) { // finds the maximal salary across the whole company const employees = _.flatten(_.map(departements, d => d.employees)) const salaries = _.map(employees, e => e.salary) return _.max(salaries) }

In this code, we take the departmentsarray and then transform it several times to get the eventual max salary.

And it apparently works. But it introduces several variables along the way which are not really needed here. The alternative is to write the whole expression in one very long row.

function maxSalary(departments) { return _.max(_.map(_.flatten(_.map(departements, d => d.employees)), e => e.salary)) }

I don’t even have to tell why it is ugly, right? It’s simply incomprehensible. Alsonote, that you have to read it from right to left, which for most of us is hard.

Until now, there was only one way to streamline that expression but only if have a luxury of using the lodash. Which by chance we do.

function maxSalary(departments) { return _(departements) .map(d => d.employees) .flatten .map(e => e.salary) .max() }

Much better, isn’t it? We don’t introduce any new variables and still, our code is pretty clean. The flow is going from top to the bottom and from left to the right.

The only downside to this approach is that you a have to pack and unpack your data. And you gotta use a 3rd party library, of cause.

Pipeline to the rescue

So finally, let’s see how pipeline helps to fix this mess.

function maxSalary(departments) { return departments |> _.map(d => d.employees) |> _.flatten |> _.map(e => e.salary) |> _.max }

The |> symbol in this code is the pipeline operator. It takes a piece of data on the left side and passes it to a function on its right side.

And this is not a new concept but rather just a syntactic sugar.

Expressions Math.sqrt(64) and 64 |> Math.sqrt are equivalent. The difference is in how we read it. With pipeline operator data flows from left to the right, and thus making it much more comprehensible without the need to introduce extra variables.

conclusion

I gotta say that this proposal is at a very early stage. There are actually two proposals now competing with each other, each has its own opinion on how async/await should work with pipelines and how to use the partial application , which is a different proposal (stage 1 as I’m writing this).

Still, I’m pretty sure it will go through pretty soon. The benefits are quite obvious especially for those who tried it in other functional languages.

I mean cmon guys, we have dragged freaking symbols into JavaScript .

Where to go from here As usual, I will be glad to connect on Twitter The official TC38 proposal 2ality tracks some other interesting features coming to JavaScript in 2019 Learn ES6 with this fantastic course by Wes Bos

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

代码区博客精选文章
分页:12
转载请注明
本文标题:The JavaScript Pipeline Operator
本站链接:https://www.codesec.net/view/611334.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(47)