I see: it uses Try::Tiny itself, and just makes the exception into its own return value.

It doesn't hide itself from the call stack, so it will make my Carp report show itself rather than my test function. Ah, but knowing that, I can just test for that instead, since the real test is that Carp reports on the caller, not some other intermediate function that was between the user-facing function and the one that died. It might be more helpful since the file/lineno will always be the same: that of the exception function itself. Perhaps a similar function can include a test of the exception string for mention of the correct location, as well.

Thanks.

—John