rspec/rspec-expectations — comment on commit d3e53109d36d1fef17b70e26e5b2adeeaf3aa078
File:  line 0
By myronmarston:

FWIW, this change broke some of my VCR specs because I construct a matcher dynamically `RSpec::Matchers::Matcher.new :respond_with, value { ... }` (see [here](https://github.com/myronmarston/vcr/blob/v2.0.0.rc1/spec/vcr/cassette/http_interaction_list_spec.rb#L131-133)).

I don't mind updating my specs to use `for_expected(value)` but this seems like a breaking change in a minor release (which is against the versioning policy we aspire to).

Is there a way we can support the old API w/ a deprecation warning while keeping the benefit of this new API?