If use Try::Tiny sees "feature_try" in the callers hint hash it can (at least) warn.
The issue, as mentioned repeatedly, is that it's impossible to check the hash at the correct time.
Elaborate edge cases for false positives and false negatives please.
What matters is whether the feature is enabled when the try call is compiled. You suggested calling at 3 or 4 other times. But that won't work. If you perform the check as these wrong times,
It can warn even there's no issue.
This happens if the feature is enabled in the lexical scope being compiled when you perform your check, but it's not enabled for the lexical scope that contains the try call.
It can not warn when there is an issue.
This happens if the feature isn't enabled in the lexical scope being compiled when you perform your check, but it is enabled for the lexical scope that contains the try call.
Provide your check, and I'll provide a case that fails.
In reply to Re^12: Try::Tiny and -E
by ikegami
in thread Try::Tiny and -E
by 1nickt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |