Alex Kuznetsov

reopened as https://github.com/kotest/kotest/pull/4159

I'll take a look.

fixed

> As I see it, this one is safe to merge, but there may be still be other ideas out there, so I'm not sure if there is sufficient buy-in....

IMO same thing should be done in several other places, such as collection matchers: if the expected outcome is failure, they shouldn't waste time describing differences

this problem persists in multiple places. this PR exposes just the tip of this iceberg. we can start making similar changes elsewhere

Can you clarify what changes in kotest are you requesting?

Is there any chance you could post complete working code to reproduce?

Is this a good use case for Kotlin's own `Result`? https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-result/