(I'm mostly just helping out with docs, but to clarify:) Would you expect it to still throw an error in the same place but with a more helpful message?

Right. Would expect it to throw an error, just something more meaningful. Something like AssertionError: async.map called with non-array value.

On Fri, Nov 21, 2014 at 5:42 PM, Beau Gunderson notifications@github.com
wrote:

(I'm mostly just helping out with docs, but to clarify:) Would you expect
it to still throw an error in the same place but with a more helpful
message?

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

Another option would be to treat a null or undefined array as an empty array. Libraries like lodash do this.

👍 I'm more of a fan of being graceful about it to be honest!

On Sat, Nov 22, 2014 at 6:27 PM, Alexander Early notifications@github.com
wrote:

Another option would be to treat a null or undefined array as an empty
array. Libraries like lodash do this.

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

@jamescarr Just to be clear, are you saying you prefer the lodash approach of treating null/undefined as empty arrays? (And what should happen if you pass in an object?)

Still crashing,

fixed adding this in line 120:
if (typeof arr === "undefined") {
return callback();
}