as I already said
> > In theory you could no feature "try" later in a sub-scope to re-enable those exports, but that's a very convoluted edge-case.
> > And I was mostly talking about "warning", warnings can be disabled if this convoluted edge-case is warranted.
Nobody does this accidentally or he/she is just dumb copy-pasting. Requiring to silence the warning with something like no warnings "masking" would be adequate. (there is no warnings category "masking" yet, but shadow exists, That's a matter of debate)
Anyway, do you have an example of a false positive which is less constructed?
FWIW: I provided an example for a false positive on reddit, if feature-try (Not Try::Tiny) is activated inside a class and was warning about name-clashes with method-names. This wouldn't make sense, because methods can't clash with built-ins.
But this is also kind of convoluted, methods are not imported and features are activated in the head lines of a scope/file, before methods are defined.
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
In reply to Re^15: Try::Tiny and -E (False Positive)
by LanX
in thread Try::Tiny and -E
by 1nickt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |