3 ms·
> You _can_ define minimum and maximum over empty sets exactly as described and get a consistent mathematical system. You can define infimum and supremum that
by thaumasiotes 7y ago
> You _can_ define minimum and maximum over empty sets exactly as described and get a consistent mathematical system.
You can define infimum and supremum that way. But I was under the impression that wherever the concept of a "minimum element" of a set is used, the minimum element of any set must be an element of that set.
So e.g. the positive reals have an infimum, 0, but no minimum. The page you link doesn't do much to dispute this idea; it uses "minimum" and "maximum" to talk about the largest and smallest elements of the lattice, but never to talk about a property that a subset of the lattice might have.
- eru 7y agoI guess you are right. Of course, the Python function named 'min' could very well implement an infimum in this case, and it would be OK. In general, there's some conventions, like using the words 'minimum' vs 'infimum'. Or stressing the property 'result of min should be an element of the input set' vs 'min on lists should behave like repeated application of min on two arguments starting with the neutral element'. The right choice depends on context. In lots of programming context, I find stressing the connection with the minimum monoid was useful.
- thaumasiotes 7y ago> Of course, the Python function named 'min' could very well implement an infimum in this case, and it would be OK. Using min(∅) = +inf and max(∅) = -inf would violate the otherwise valid constraint that min(x) ≤ max(x). I'd be a little uncomfortable with it for that reason. > The right choice depends on context. Definitely.
- eru 7y ago> Using min(∅) = +inf and max(∅) = -inf would violate the otherwise valid constraint that min(x) ≤ max(x). I'd be a little uncomfortable with it for that reason. Excellent point! Funny enough, we have the same with 'any' and 'all': For most lists of booleans: all(l) ≤ any(l). Or equivalently all(l) implies any(l). But that property is broken for empty lists. Hmm, I think I might understand the case for `all([]) == False` a bit better now. Though I still disagree with it.