### 3.2.0 / 2015-02-03
[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v3.1.3...v3.2.0)
Enhancements:
* Treat `any_args` as an arg splat, allowing it to match an arbitrary
number of args at any point in an arg list. (Myron Marston, #786)
* Print diffs when arguments in mock expectations are mismatched.
(Sam Phippen, #751)
* Support names for verified doubles (`instance_double`, `instance_spy`,
`class_double`, `class_spy`, `object_double`, `object_spy`). (Cezary
Baginski, #826)
* Make `array_including` and `hash_including` argument matchers composable.
(Sam Phippen, #819)
* Make `allow_any_instance_of(...).to receive(...).and_wrap_original`
work. (Ryan Fitzgerald, #869)
Bug Fixes:
* Provide a clear error when users wrongly combine `no_args` with
additional arguments (e.g. `expect().to receive().with(no_args, 1)`).
(Myron Marston, #786)
* Provide a clear error when users wrongly use `any_args` multiple times in the
same argument list (e.g. `expect().to receive().with(any_args, 1, any_args)`.
(Myron Marston, #786)
* Prevent the error generator from using user object #description methods.
See [#685](https://github.com/rspec/rspec-mocks/issues/685).
(Sam Phippen, #751)
* Make verified doubles declared as `(instance|class)_double(SomeConst)`
work properly when `SomeConst` has previously been stubbed.
`(instance|class)_double("SomeClass")` already worked properly.
(Myron Marston, #824)
* Add a matcher description for `receive`, `receive_messages` and
`receive_message_chain`. (Myron Marston, #828)
* Validate invocation args for null object verified doubles.
(Myron Marston, #829)
* Fix `RSpec::Mocks::Constant.original` when called with an invalid
constant to return an object indicating the constant name is invalid,
rather than blowing up. (Myron Marston, #833)
* Make `extend RSpec::Mocks::ExampleMethods` on any object work properly
to add the rspec-mocks API to that object. Previously, `expect` would
be undefined. (Myron Marston, #846)
* Fix `require 'rspec/mocks/standalone'` so that it only affects `main`
and not every object. It's really only intended to be used in a REPL
like IRB, but some gems have loaded it, thinking it needs to be loaded
when using rspec-mocks outside the context of rspec-core.
(Myron Marston, #846)
* Prevent message expectations from being modified by customization methods
(e.g. `with`) after they have been invoked. (Sam Phippen and Melanie Gilman, #837)
* Handle cases where a method stub cannot be removed due to something
external to RSpec monkeying with the method definition. This can
happen, for example, when you `file.reopen(io)` after previously
stubbing a method on the `file` object. (Myron Marston, #853)
* Provide a clear error when received message args are mutated before
a `have_received(...).with(...)` expectation. (Myron Marston, #868)
1f6ad46e71