From: Martin DeMello <martindemello@...>
Date: 2010-09-01T22:38:38+09:00
Subject: Re: why no assert_not?

On Wed, Sep 1, 2010 at 2:37 PM, Brian Candler <b.candler@pobox.com> wrote:
>
> But I think the issue is moot, because writing custom asserts is a
> perfectly standard thing to do. That is, just write
>
>  def assert_not(bool, *rest)
>    assert(!bool, *rest)
>  end

Yeah, but this one seems universal enough that it ought to be there by default.

martin