Right now there're tons of libs relying on Hamcrest matchers, such as rest-assured, which is also has Kotlin support.
When I saw your library first time I was pretty surprised. It was until I realised that Hamkrest is not compatible with Hamcrest interfaces. That's really disappointing, as all of your syntactic sugar renders useless for me. The only question is why?
Maybe is it possible to make your awesome lib compatible with Hamcrest?
If not, don't you know any alternatives?
Right now there're tons of libs relying on Hamcrest matchers, such as rest-assured, which is also has Kotlin support.
When I saw your library first time I was pretty surprised. It was until I realised that Hamkrest is not compatible with Hamcrest interfaces. That's really disappointing, as all of your syntactic sugar renders useless for me. The only question is why?
Maybe is it possible to make your awesome lib compatible with Hamcrest?
If not, don't you know any alternatives?