Paul Evans

These are certainly some excellent reasons why your code style guide, reviewer notes, etc.. should suggest the use of safer mechanisms like MOP/meta, over plain globref hackery. But by itself...

I was hoping we'd add all the functions in the same release, even if not the same actual commit. It won't matter too much if we add a few at...

If we want a `first` I can consider that, but lets do that in its own discussion. I wanted to clarify here first what the feature/warning name would be, and...

My thinking here was that the aliasing behaviour is basically never used intentionally and any time it comes up it's always been a bug that has caused accidental modification. The...

> Why not? Many people love to use the `EXPR` version of `map` and `grep`. This was already mentioned in the original PPC0027. Avoiding that syntax avoids a bunch of...

> †. ... though `first` seems like a sketchy name, since `last SAME_BLOCK, SAME_LIST` isn't going to give you the last match `first` is already very-well established as the name...

As the idea for read-only copies of data in `$_` seemed unpopular, I've moved it into a suggestion for Future Scope; we can come back and think about that as...

> We discussed this during the PSC meeting today. Assuming we're not constrained in the ever-growing number of feature flags, there should simply be one flag per symbol (so `any`,...

My personal thought is that I think it's fine. People really shouldn't be doing `use feature ':all'` anyway, because that's just a footgun waiting to happen. Yes it is a...

PR https://github.com/Perl/perl5/pull/22773 is currently paused awaiting a resolution on this question. At present it's implemented with two separate feature flags, named `all` and `any`. Despite the potential for confusion, I...