Good point. However setting
def __bool__(self): return self.nonEmpty
Maybe a warning would be appropriate? (as is the case with ndarrays)
Isn't that consistent with the built-in `list`, though, because `bool([False, False])` is True?
For example, when calling
Array((x, y), (z, w)).index((z, w))
bool(Array((x, y)).__eq__((z, w)))
= bool(Array(False, False))
You're right that it would be more clear if __bool__ would behave similarly, but since Array computes operations element-wise, it isn't possible.
If you used `all()` in your implementation instead, you could be compatible with the idiomatic use of `bool(my_list)` and the _very_ common `if my_list:` structure could be used with Arrays too (like most people probably would expect from a "better list type")
Regardless, Pandas struggles with the same problem, so you are at least in good company :)