Regarding the issues with colliding matcher method...
# strikt
r
Regarding the issues with colliding matcher method signatures. I can solve it by creating specific types (with an associated
expect
overload) such as
IterableAssertionBuilder
,
MapAssertionBuilder
, etc. then using those as the targets for the extension methods. It means more boilerplate when creating matcher extensions for new types but it does allow for matchers with the same names / parameters on different assertion targets.