Kotlin-style pipelines about proposal-pipeline-operator HOT 3 CLOSED

Adding anything to Object.prototype is not a good idea :-) it won't work for null objects, in particular, and it wouldn't make sense as an operation on booleans, numbers, symbols, regexes, etc.

Adding them to Function.prototype would be more reasonable, and that already has an .apply.

from proposal-pipeline-operator.

Yup, we can't add to Object.prototype. And if it's not on the prototype you don't get chaining, which makes it extremely unergonomic.

@andyearnshaw One can also look at this very proposal, which has this example in its README.

from proposal-pipeline-operator.

Take a look at the extensions proposal. It would allow operations like this without having to extend existing prototypes:

Object.keys(envars)
  .map(envar => `${envar}=${envars[envar]}`)
  .join(' ')
  ::let(it => `$ ${it}`)
  ::let(it => chalk.dim(it, 'node', args.join(' '))
  ::also(it => console.log(it));

from proposal-pipeline-operator.