equalTo() Should Not Force Type Match of Actual to Compile about javahamcrest

[sf105]

you have a point. There are tradeoffs in that the typed version will catch some mistakes at compile time and works better with jmock (our original client). I'm now beginning to think that jMock should have had its own matcher methods, but it's a bit late now.

[EarthCitizen]

What will break if the signature of equalTo() is changed now? Would it affect a small number of users or create a large inconvenience for most?

[sf105]

People using asserThat directly will be fine, apart from occasionally missing a helpful type clash when refactoring. People using Hamcrest with JMock (and maybe other mock frameworks) will get compilation failures.

[EarthCitizen]

What do you think a good solution would be?

[npryce]

The only solution is to add another matcher factory method. E.g.

isEqualToObject(Object o) -> Matcher

[npryce]

Implemented in master.