2 ms·
If you view any and all as reductions any([x, y]) == x or any([y]) == x or y or any([]) all([x, y]) == x and all([y]) == x and y and all([]) then any([])
by erik_seaberg 7y ago
If you view any and all as reductions
any([x, y]) == x or any([y]) == x or y or any([])
all([x, y]) == x and all([y]) == x and y and all([])
then any([]) must be false (otherwise x and y would never matter), and all([]) must be true.
In the query API you're describing, does {topic1, topic2} find datasets on (topic1 OR topic2), or is it (topic1 AND topic2)? That's what determines whether more topics means more or fewer results, and whether {} should correctly find nothing or everything.
- eru 7y ago> [...] then any([]) must be false (otherwise x and y would never matter), and all([]) must be true. Yes, I know. My problem is with: > Another reason we must have `all([]) == True`, because `any([])` should obviously be `False`. Argument is of the form 'A, because B'. But I don't see how B is any more obvious than A here. They seem about equally obvious.