👍

@megawac Should we merge this now, or wait until the modularization is complete? (That branch is almost ready to be merged, just some package questions remaining).

Either way is fine, I can rebase/cherry-pick any commits onto the
modularizations branch

On Tue, Feb 2, 2016 at 5:57 PM, Alex Early notifications@github.com wrote:

@megawac https://github.com/megawac Should we merge this now, or wait
until the modularization is complete? (That branch is almost ready to be
merged, just some package questions remaining).

—
Reply to this email directly or view it on GitHub
#1018 (comment).

@aearly @megawac I could send a new pull request against the modularization branch and close this one, what do you think?

That would be really helpful.

Modularization is now on master, so no weird branch to consider now!

Thanks for the heads up, I will submit a new pr soon.

Cool @jorgebay. By the way, it might make sense to implement this via async.some as you can accomplish the same result with some

Yeah, but heads up, we also want to change the arguments for some and family to take an error in the callback. #118