Adds support for variable argument lists as operation input
Version bump: v0.4.0 -> v0.5.0
Release v0.5.0
Fixes ComposedOperation option parsing
Version bump: v0.5.0 -> v0.5.1
Release v0.5.1
Adds an outline for the different testing scenarios regarding the new operation input handling
Improves output of custom matchers
Extends matchers to support instantiating operation instances themselves and provide them with input if necessary

Meaning, matchers can now work with classes or instances.
Adds pry as a development dependency
Extracts common behavior of SucceedToPerform and FailToPerform matchers into a common super class
Improves the input processing and makes it more predictable
Fixes specs that have been breaking because of the new input processing
Adds specs to ensure that input propagation in processing pipelines works as expected
Updates README to reflect changes introduced by the new way of input parameter parsing
Version bump: v0.5.1 -> v0.6.0
Release v0.6.0
Input splatting for ComposedOperation

Changes the way ComposedOperations expand the operation input. Removes
the call to Array() as it does convert everything that is representable
as an Array to an Array but according to this objects definition. :(
Version bump: v0.6.0 -> v0.7.0.pre
Specs for forwarding enumerable objects in ComposedOperations

Adds two currently failing specs that describe forwarding enumerable objects or in general objects that respond to #to_a in a ComposedOperation. The tests specify that objects of this kind should not be accidentally converted into an array while moving forward through the pipeline.