satisfy conflict with rspec2

[tight]

rr's satisfy wildcard matchers conflicts with rspec2's one

In order to use rr's satisfy, you can just add a method in RR::Adapters::RRMethods :
module RR::Adapters::RRMethods
def rrsatisfy(&block)
RR::WildcardMatchers::Satisfy.new(block)
end
end

You can now use
mock(object).foobar(rrsatisfy {|arg| arg.length == 2})
object.foobar("xy")

[mb-dev]

I just encountered that. I wonder how it's not fixed by now

[mcmire]

For future reference: all RR methods are aliased as rr_*, so in this case you can use #rr_satisfy.

[mcmire]

I am reopening this.

The reason why this is happening is because in RSpec, in order to set up an example group, two things happen:

1. a module which represents the mock framework (RR) is mixed into the example group
2. a module which represents the expectation framework (rspec-expectations) is then mixed into the example group

(source)

So, RSpec's #satisfy is indeed overriding RR's #satisfy.