redding/assert — pull request #206 by jcredding (2014-07-08 17:19:25+00:00)
Title: Better arity error messages

This adds better error messages to the arity exceptions that are
raised when stubbing a method or calling it with the wrong arity.
This should help with identifying the issue and what needs to be
addressed. The message now clearly explains the method that was
called/stubbed with the wrong arity, how many args it expected
and how many it got.

@kellyredding - Ready for review. Here's a sampling of the error messages that you can get (I generated these using the system tests:

```
arity mismatch on `noargs`: expected 0, stubbed with 1 (Assert::StubArityError)
arity mismatch on `noargs`: expected 0, called with 1 (Assert::StubArityError)
arity mismatch on `withargs`: expected 1, stubbed with 0 (Assert::StubArityError)
arity mismatch on `withargs`: expected 1, called with 0 (Assert::StubArityError)
arity mismatch on `withargs`: expected 1, stubbed with 2 (Assert::StubArityError)
arity mismatch on `withargs`: expected 1, called with 2 (Assert::StubArityError)
arity mismatch on `minargs`: expected at least 2, stubbed with 0 (Assert::StubArityError)
arity mismatch on `minargs`: expected at least 2, called with 0 (Assert::StubArityError)
arity mismatch on `minargs`: expected at least 2, stubbed with 1 (Assert::StubArityError)
arity mismatch on `minargs`: expected at least 2, called with 1 (Assert::StubArityError)
```