From: Josh Cheek <josh.cheek@...>
Date: 2010-07-31T03:55:03+09:00
Subject: Re: [].all?{} and [].any?{} Behavior

--001485f03db0766a2e048c9f5e28
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jul 30, 2010 at 10:49 AM, Rick DeNatale <rick.denatale@gmail.com>wrote:

> module Enumerable
>  def non_vacuous_all?(&b)
>    !empty? && all?(&b)
>  end
> end
>
> [3].all? {|element| element == 3 }  # => true
> [3].all? {|element| element != 3 }  # => false
>
> [].all? {|element| element == 3 }   # => true
> [].all? {|element| element != 3 }   # => true
>
> [3].non_vacuous_all? {|element| element == 3 }  # => true
> [3].non_vacuous_all? {|element| element != 3 }  # => false
>
> [].non_vacuous_all? {|element| element == 3 }   # => false
> [].non_vacuous_all? {|element| element != 3 }   # => false
>
> [].any? {|element| element == 3 }   # => false
> [].any? {|element| element != 3 }   # => false
>
> There may be a better name than non_vacuous_all? but I can't think of one.
>
>
How about #appall? to imply that it is a pessimistic implementation of #all?
:)

--001485f03db0766a2e048c9f5e28--