proposal-partial-application

Yeah. I dislike the hack pipes proposal because it introduces a bunch of syntax that only works mid pipe. F# style and a separate partial application proposal that could work anywhere in js (instead of just in a pipe) seems preferable to me. https://github.com/tc39/proposal-partial-application

Currying is nice but in practice it’s rather esoteric in the JavaScript ecosystem. I’ve only seen currying being used (if at all) when transforming data with utility libraries like ramda[1]. What makes it worse it that partial application is rather cumbersome to type. Lucky for us there is a partial application proposal, albeit still in stage 1, which makes partial application—to make functions curried—a lot easier[2]. [1] https://ramdajs.com/docs/#curry [2] https://github.com/tc39/proposal-partial-application

There's a proposal for this: https://github.com/tc39/proposal-partial-application

FYI, you can achieve the same thing with F# pipelines + partial application proposal [1] input |> func(?, 2) input |> func(1, ?) While hack's placeholders work exclusively in pipelines, the partial application proposal can be used with any function "123" .split("") .map(parseInt(?)) // make sure radix param is not set [1] https://github.com/tc39/proposal-partial-application

There is currently a proposal to bring syntax support for partial application to JS: https://github.com/tc39/proposal-partial-application/blob/ma...

Outside of type annotations, Typescript never supports syntax that isn't in an ECMAScript standard or a popular proposal. That said, there is a Stage 1 TC39 proposal for partial application. https://github.com/tc39/proposal-partial-application

If you really like the idea of syntactic partial application in your JavaScript, you should check out the stage 1 tc39 proposal for exactly that: https://github.com/rbuckton/proposal-partial-application It's slowly being worked through the committee, so if you care enough about the feature, you should consider voicing your support.

Has anyone read the semantics of the linked partial application proposal [0]? > Note that this also means that more involved references are captured in their entirety and should be stored in a local variable if they may have unintended side-effects should the partially applied function result be called more than once const a = [{ c: x => x + 1 }, { c: x => x + 2 }]; let b = 0; const g = a[b++].c(?); b; // 0 g(1); // 2 g(1); // 3 b; // 2 `a[b++].c` is not evaluated until the partially applied function `g` is called. Event `a[b++]` and `b++` are not evaluated. It is unclear to me when `const g = Math.random().toFixed(?)` would evaluate `Math.random()`. [0]: https://github.com/rbuckton/proposal-partial-application#sem...