This utility is useful enough to be shareable, but I share Justin's concern. I originally suggested that we call it "testing", so the library would be called "quiver.testing" making it really obvious that it's not meant for production use. Our project mandates checked mode during all development so we could use it to enforce checked mode (or at least put a big red warning "Running in unchecked mode!!!") in unit-tests and in debug builds.