Re: Type confusion, array and object
>Because array.filter is a provided function a user looking at a.filter()
> > There is confusion with array.filter.
> But it's an object not an Array
would be likely to assume a is an array. This could lead to errors or lost
time. (That is the logic anyway)
[Non-text portions of this message have been removed]
- So the answer is that the name space should be considered global because filter is used somewhere it can't be used anywhere else?
Originally some sort of rudimentary type checking sounded useful but I think I'm going to I'm going to opt out if this is the direction it's going.