Kyle Simpson

decide on which libs will be used

2

Need to investigate "acorn" and "escodegen" libs, as those are what I think I'll be using, but not positive yet.

Check out the iterators in [itiriri-async](https://github.com/labs42io/itiriri-async#complete-list-of-methods) and see if any of them would be useful to support in Fasy.

Add note about how [itiriri-async](https://github.com/labs42io/itiriri-async) handles **lazy async iteration**.

Feature: support async-generators (`async function*`)

6

[Async-generators are stage3](https://github.com/tc39/proposal-async-iteration#async-generator-functions), so fairly likely to land in JS. Seems like **fasy** should support them eventually, probably sooner than later. **[UPDATE]:** They landed in ES2018. For example: ```js FP.serial.map(async...

Like Ramda: https://ramdajs.com/docs/#reduced

Is there a way to make operations cancelable?

2

Explore some way to combine/bring in [CAF](https://github.com/getify/CAF) (cancelable async functions) capabilities so that fasy's async iterations are optionally cancelable. This might need to be a separate namespace where the API...

Like Ramda: https://ramdajs.com/docs/#reduced

interesting quirk with named currying

4

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 =...

Inspired by the `curryN(..)` from Ramda, these two would be loose-curried for a specified number of input functions. Allows lazy composition.