Hi All,

I propose that we remove the none() step from Proposal 3 (
https://github.com/apache/tinkerpop/blob/master/docs/src/dev/future/proposal-3-remove-closures.asciidoc#none).
After looking into several languages that support list functions (including
Groovy, Python, LINQ, and Clojure), most of them don't include a "none"
function. Instead, "none" functionality is achieved through not "all". This
provides a sensible way to handle an empty list as "all" would return true
and "any" would return false. Given that our new approach to "all" will
take a predicate in as a parameter, a user could negate the predicate to
achieve the same result. Users are likely already familiar with not having
access to "none" function as it probably doesn't exist in their language of
choice. It's also easy to add the "none" function later if we find that
users expect it to be in the language.

Please let me know what you think about removing the none() step.

Thanks,
Ken

Reply via email to