On Wednesday, 27 February 2013 at 17:37:34 UTC, H. S. Teoh wrote:
[...]
Again, my point was not that it's a bad idea to have isBlank.
My point
was that if you add isBlank, then isPresent is redundant, and I
would
argue even harmful. The best APIs are minimal ones, that
provide all
*necessary* primitives with minimal overlap between them.
T
I agree.
I can only see a need for "isPresent" (or the opposite) only if
it was made clear that isPresent does something different than
!isBlank.
If you continue to use isPresent, then I suggest that it is
implemented as a convenience wrapper around !isBlank to make sure
that changes to isBlank automatically propagate back to isPresent.
--rt
