v1.4.0

Permit implementations to splat their parameters if unused

When writing mocks and passing those to an implementation, often the mocking library will define the methods as def foo(*args, **kwargs, &block) such that they can inspect the arguments and assert upon them later. With this change, parameters that are not directly used by the implemented method can be splatted. When calling the implementation through the interface, types of course will still be strictly checked as they are today. This loosens the strictness of Strict::Interface slightly in the regard that the method does not have to be an exact match, but rather must be able to be safely called by the interface instance.

What's Changed

• Bump debug from 1.6.2 to 1.6.3 by @dependabot in #28
• Bundle Update by @kylekthompson in #31
• Permit implementations to splat their arguments if unused by @kylekthompson in #32

Full Changelog: v1.3.1...v1.4.0