Fix generated docstring when Class#inspect changed
Remove some unnecessary test code
Don't leak a class out of the spec
Use stub_const to have a user class and show intent
Remove no-longer-relevant comment
Make the error message more useful when using match_array

* Now the error message will let you know if you're trying to match an
  array against something that isn't an array-like thing.
* Closes #186
* Fixes #185
Merge pull request #184 from mortice/implicit-docstring-for-instance-of-matcher

Fix generated docstring for BeAnInstanceOf when Class#inspect changed
Update changelog.

[ci skip]
Use 'empty?' instead of 'any?' and 'none?' in order to match 'nil' and 'false' as argument values
Merge pull request #187 from nanocity/yield_arguments

Use 'empty?' instead of 'any?' and 'none?' to match 'nil' and 'false'
prep for 2.12 [ci-skip]
Updates to rake 10
bump version to 2.12
Fixes changes link
OperatorMatcher considers ancestor chain

* Related #191
Merge pull request #192 from alindeman/operator_registry_considers_ancestors

OperatorMatcher considers ancestor chain
Provide a clear failure message when using `{}.should =~ {}`.

The match_array matcher (delegated to by `=~` for enumerables) is
not meant to be used for hashes, but the `should =~` syntax doesn't
make that obvious. Previously, you would get a failure like:

     Failure/Error: actual.should =~ actual
       expected: {:foo=>"bar"}
            got: {:foo=>"bar"} (using =~)

...which is pretty confusing. Our `match_array` matcher already
includes handling for invalid arguments (such as hashes) to return
a clear failure message, but it wasn't being used for an expression
like `{}.should =~ {}` because it was only registered as an operator
matcher for `Array`. This changes it so that it is registered as an
operator matcher for any Enumerable. This improves the failure message
for enumerable types like hash and set, but on its own, it could cause
breakage for things like 1.8 strings that are Enumerable but also
define a reasonable `=~`.  The fix here changes the operator matcher
delegation logic so that it only delegates to the registered matcher
if the object has the generic Kernel implementation of the operator.
If it has a more specific implementation, we assume the user actually
wants to match using the given operator itself.

Fixes #191.
Merge pull request #193 from rspec/hash_match_array_failure

Provide a clear failure message when using `{}.should =~ {}`.
Cleanup whitespace
Allow custom matchers to use #match built in

Addresses problem with dispatching the #match matcher from within a
custom matcher. (Wow... what a mouthful) See Issue #188.