Before I'm coming up with yet another issue: I'm i...
# kotest-contributors
o
Before I'm coming up with yet another issue: I'm investigating the possibility of improving clues, which would include providing them for exceptions not thrown by Kotest (e.g. Kotlin Power-Assert, assertions thrown in production code without access to Kotest functions, ...). Is there a particular reason why (most) clues are attached to assertions at throw time (via
failure
) instead of a catch block inside
withClue
?