Respond_to matcher


#1

I noticed this strange behaviour in a spec, and was wondering if it was
considered a bug (it certainly took me by surprise):

The respond_to matcher specs seem to show this behaviour as intended:

Scott