[rspec-users] != again

Pat Maddox
Mon, 02 Jun 2008 18:01:47 -0000

On Sun, Jun 1, 2008 at 1:55 PM, David Chelimsky <dchelimsky at gmail.com>
wrote:
> On Jun 1, 2008, at 12:17 PM, Matthias Hennemeyer wrote:
>
>> Hey!
>>
>> I have implemented a quick solution for the should != .. , should !~
...
>> ''problem''.
>> It uses source code inspection (I think it''s the only way) and
i''ve done
>> some
>> benchmarking to see if it''s really that slow.
>>
>> A direct comparison of
>> running ''1.should == 1''
>> with the unmodified rspec source against the rspec-version with source
>> inspect
>> shows that the latter is 7 times slower ... :(
>>
>> But benchmarks with ''1.should == 1'' inside a real
example file are
>>  showing ''only''
>> an overall speed decrease of 15% to 50%. That is still bad but having
lots
>> of people
>> consider the passing of ''1.should != 1''  an rspec bug
is bad too.
>
> RSpec is already getting dinged for being slower than test/unit. Making it
> run any slower than it already does is a deal breaker for me.

What about showing an ugly warning in the test runner?  != is a funky
edge case that can really bite people.  It''d be nice to have it fixed,
but then tell the programmer to change it to == because of
performance.

Pat