--- Comment #2 from Jonathan M Davis <> 2010-06-28 
21:20:24 PDT ---
I'd love any() since it's nice and clear. It's just that as far as I can tell,
the version of canFind() which takes only a range (along with the predicate) is
exactly what any() would do. There may a difference, but I don't know what it
would be. But even if there isn't, it wouldn't hurt my feelings any to have
any() on top of canFind(). It just seemed likely that someone would complain
that it was cruft to have any() when canFind does exactly what any() would do.
I would prefer an explicit any() though, since it would be clearer in code what
you intended to do.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to