-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reduce callback isn't really optional #1223
Comments
Yeah, actually looking into this a lot of methods are documented to have optional callbacks when they are clearly required These are the ones I've identified are incorrectly documented:
|
Should these be optional or not @aearly |
In my case it's helpful if they're optional. At each step of the reduce I
can delete a file until a certain amount of data has been removed. The
total bytes remaining to be deleted are passed along in the memo. I don't
care about the final result - just the side effect of files getting deleted
- so I'm using an empty callback.
|
Yeah, they should all be optional. I do think it's odd that you would use |
I think |
Yeah, there'd be no reason to use |
What version of async are you using?
1.5.2 (but the offending code seems to still exist in master)
Which environment did the issue occur in (Node version/browser version)
node v0.10.29
What did you do? Please include a minimal reproducable case illustrating issue.
The documentation says the callback is optional, so I should be able to do:
What did you expect to happen?
What was the actual result?
The text was updated successfully, but these errors were encountered: