and a few months later: our @EXPORT ... Are you sure that you, even if you're already a veteran, will never make this mistake?

comments next to a space separated list of barewords?

Yes, I am 100% sure I will never make this mistake

the same as I am sure I will never type "#oops," and not want the "#" and "," as part of the string, and then come back 20 years later and type "# oh yeah , yeah yeah yeah " and expect to get a list instead of a string

but even if I made the mistake, Exporter whose job it is to handle @EXPORT, would catch this the first time the module was used, like when the tests were run, and die  Can't export symbol: # at junk.pl  line 21

But hey, documenting design indecision in comments? That doesn't belong in comments, it belongs in official documentation, so I'm more than 100% sure, i'm 200% sure :D

Does the programmer make a typo or does he really mean setting $Foo::bar? When something is (indeed) a warning, there's always the possibility that the warning is incorrect in that it does not align with what the user means.

congratulations, , even I won't argue that one doesn't belong, but only because its exceptional

Solution to that one isn't disable warnings lexically its  $double::up = $double::up = "for silence";

Anyway , haukex was faster to perlcritic policy, but I would have used xpaths instead

perlcritic is where this type of extra help belongs , warnings is all full up