froebel

(a: string) => a+' ')(3)` is as clean as I've ever seen it get. And to use it in an ad-hoc way for left-to-right readability (and for code that will be maintained by those who think curry is just a tasty dish), it's trivial to implement an applyPipe on top: applyPipe('foo', strip, title, (s: string) => `${s}: bar`) OP - it would be great to have that, or something named slightly better, out of the box!

type that TypeScript cannot handle. A common workaround for this is to define pipe's type separately for every number of arguments it can take. This is for example how RXJS defines its pipe function: https://github.com/ReactiveX/rxjs/blob/f174d38554d404f21f98a... Other common solutions are to make concessions like requiring all functions to have the same return type or letting pipe only take one function at a time and returning an object with methods to add another function and invoke the chain. None of these solutions are satisfying in my opinion. I think I've finally found an implementation that fulfills all these criteria. The argument and return types of passed in functions are correctly enforced (no matter the number of passed-in functions) and the pipe function returns a function that accepts the arguments of the first function, invokes all functions in turn with the result of the last, and correctly returns the type of the last function of the chain. Including asynchronous functions in the chain works to: if a function returns a promise that promise is resolved before being passed into the next function and the function returned from pipe will return a promise as its type. There is one disadvantage to the implementation that I'm aware of: When passing in anonymous functions, the types of their arguments can not be inferred if they aren't annotated. That means that pipe(() => 10, n => n.toString()) would return the type () => any but I think that's an acceptable tradeoff because when annotated pipe(() => 10, (n: number) => n.toString()) it will return the correct type () => string Thought the implementation might be worth sharing here in case it's useful to someone else and because it's an interesting problem to solve in TypeScript's type system. If you have any suggestions on how to improve the function's typing or know of any better implementations, I'd appreciate it if you would let me know! Edit: I meant to link to the pipe part of the readme, but I see the link is just to the repo, that's unfortunate. Here is the relevant section of the readme: https://github.com/MathisBullinger/froebel#pipe and here the implementation: https://github.com/MathisBullinger/froebel/blob/main/pipe.ts...