On Feb 13, 2011, at 7:59 PM, Eli Barzilay wrote:

>> In any case, wouldn't
>> 
>> (test E /=> #f)
>> 
>> be even shorter and clearer?
> 
> I find `/=>' extremely confusing.  If it means a simple "does not
> evaluate to", then what happens when E throws an error?

There are two things "/=>" could mean: "does not evaluate to", or "evaluates to 
something other than".  I'd lean towards the latter, for the reason you point 
out.  But whichever, as long as it's documented.

Stephen Bloch
[email protected]


_________________________________________________
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/users

Reply via email to