Skip to content
This repository was archived by the owner on Jan 26, 2022. It is now read-only.

Address userspace one-liner anti-argument #1

Closed
js-choi opened this issue Oct 2, 2021 · 1 comment
Closed

Address userspace one-liner anti-argument #1

js-choi opened this issue Oct 2, 2021 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@js-choi
Copy link
Collaborator

js-choi commented Oct 2, 2021

These helper functions are simple, and they can be reimplemented easily in userspace. So why standardize them? The explainer needs to address this top objection.

These helper functions are very common. It would improve developer ergonomics, code clarity, and maybe optimizability if they were standardized.

These functions wouldn’t make JavaScript a kitchen-sink language. These are just a few already-frequently-used convenience functions.

The explainer needs to say all this as compellingly as it can.

@js-choi js-choi added the documentation Improvements or additions to documentation label Oct 2, 2021
@Avaq
Copy link

Avaq commented Oct 3, 2021

As briefly mentioned in tc39/proposal-pipeline-operator#233 (comment), when I raised this concern, I personally thought the scope of this proposal would focus on combinatory logic. With the addition of the variadic pipe, compose, and pipeAsync functions, the userland concern, at least for me personally, has been alleviated.

@js-choi js-choi closed this as completed in 81dbd6c Oct 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants