Ken Williams wrote:
The concern I have about the namespace is that the pragma 'strict' suggests that when you use it, you must eliminate ambiguities in your code so that the compiler doesn't have to guess what you mean. That's not what you're doing here, you're erecting new rules to enforce API boundaries between library and caller.
"stricter::can" ? Or, since it's overriding UNIVERSAL, UNIVERSAL::can::strict
