fixup!

rspec-collection_matchers' `have` matcher is very sensitive to chained
methods called on it and considers it a model name. When we happen to
call `supports_value_expectations?` on `have(3).players`, it is
overriding the previously passed model name (`players`).

lib/rspec/expectations/expectation_target.rb

@@ -116,9 +116,11 @@ def enforce_value_expectation(matcher)
       end
 
       def supports_value_expectations?(matcher)
-        matcher.supports_value_expectations?
-      rescue NoMethodError
-        true
+        if matcher.respond_to?(:supports_value_expectations?)
+          matcher.supports_value_expectations?
+        else
+          true
+        end
       end
     end
 
@@ -150,9 +152,11 @@ def enforce_block_expectation(matcher)
       end
 
       def supports_block_expectations?(matcher)
-        matcher.supports_block_expectations?
-      rescue NoMethodError
-        false
+        if matcher.respond_to?(:supports_block_expectations?)
+          matcher.supports_block_expectations?
+        else
+          false
+        end
       end
     end
   end