FPO
FPO copied to clipboard
getify
FP library for JavaScript. Supports named-argument style methods.
I wanted to float an idea to take advantage of additional benefits from destructured object param function signatures... But first I want to include my thoughts on the pattern. Here's...
This looks great! I was wondering about how one could either use only the functions needed via tree shaking, or will the build process allow a custom build to be...
Like Ramda: https://ramdajs.com/docs/#reduced
Just got bitten by this quirk, but not sure if it's a bug or if we should leave it alone... thoughts? ```js function foo({x,y,z}) { console.log(x,y,z); } var f =...
I'd like to use one of the functions in a project - but I don't want to depend on everything in this package. For e.g. I'd like to use [apply](https://github.com/getify/fpo/blob/master/docs/core-API.md#fpoapply)....
Inspired by the `curryN(..)` from Ramda, these two would be loose-curried for a specified number of input functions. Allows lazy composition.
Some interesting things from Ramda to consider adding to FPO: * `_arity(..)` is used to create a function with a proper `.length`, from the results of utils like `curry(..)`, etc...
Hi Kyle, love this lib! I've [thought about this in the past as well](https://gist.github.com/gunar/1268c997ca66343f060dbca07aee67bd). From that discussion, it seems that it'd be better for named curry to accept the argument...
