In case it helps someone else: I couldn't find if the method was redefined
by another class, but applying this patch solves the issue:
https://github.com/rspec/rspec-core/commit/41c20dfc4e8bc99b6c7bba1e074883614d2aa656
(using inject instead of reduce).
I'm on ruby 1.8.7 (2010-08-16 patchlevel 3
Hi David,
reduce has a number of different forms, one of which is collection.reduce {
> ... } (with a block but no args).
>
My best guess is either your app or another lib/gem is redefining reduce.
> Possible?
>
well I don't know the codebase enough yet, but I guess yes, it's definitely
possib
On Nov 8, 2011, at 10:45 AM, Thibaut Barrère wrote:
> Hello,
>
> I'm a bit puzzled on this one.
>
> I'm getting a wrong number of arguments on a reduce call (full stack trace
> here: https://gist.github.com/1348309).
>
> Any idea where it could come from? (I tried with 2.7.1 and 2.8.0.rc1).
>
