Hi Stevie, thanks, yeah, that would work. But I assume that the Type::* modules do that under the hood ... If I had to eval a test to print a message, there wouldn't be much point in using the whole Type::* infrastructure....

As the docs say, the default message is a "vaguely sensible default." So if I can't get my messages to print, it won't be the end of the world. But it's frustrating that it only stops working in a certain case.

I'm going to see if I can figure out how to fix it in Type::Tiny before I give up :)