Andy Lester

There are a few use cases here we've discussed. * @SparkeyG only uses Perl > 5.20, and he wants to be able to use match variables like `$&` without Perl::Critic...

We need to resolve the documentation discussion in #852. We need to explain to the user what the difference between STDERR and *STDERR is. As I said in #852: "Someone...

No, but now I'm wondering why I wasn't getting my code detecting it. I'll have to try to recreate it.

Any examples of bad code that this was intended to catch? Any tests?

What about bad code that you've discovered in the wild? I'm trying to imagine someone doing something like ``` my @foo = grep { $_ == 3 or next }...

OK, thanks. The policies make sense that you wouldn't want to do these things, but I'm less inclined to add policies for things that people don't actually do. Maybe someone...

This seems reasonable to me.

I shudder to think what would happen if we just changed it from requiring "use base" to "use parent". But I do think that it's what folks ought to do....

Then again, if all we do is change the recommendation to be "parent" instead of "base", that's not so bad.

Isn't there currently a policy out there that catches "use base" and recommends "use parent" instead?