Philippe Bruhat (BooK)

> Should it be called list_utils if it only includes any and all? Why not simply `any_all`? Possibly `first` (as a short-circuiting version of `any`) could be part of the...

What about `$^a` and `$^b`? They have a the benefit of an obvious identification to the left and right side of an operation. And all the `$^` variables are already...

> Differing in behavior from grep/map would be extremely surprising. If map/grep use aliases, any/all should as well. My second-hand memory of this is that one is using aliases and...

> `$_` is an alias inside both grep and map. grep returns a list which contains aliases to the input list elements. map returns copies. OK, that's what my memory...

> The fact that these new operators already don't support the `op EXPR, LIST` deferred expression syntax Why not? Many people love to use the `EXPR` version of `map` and...

> What is the decision on feature flag name for these operators? Are we sticking with `any_all` for this, and accepting that `first` or `reduce` or whatever would each get...

> Though perhaps we should add some specific wording in the docs pointing out the case for `all`, that it is one specific symbol called "all", and not all of...

Writing `use VERSION` as the first line of a Perl file should be understood as _declaring_ which version of the Perl _language_ the rest of the file is written in....

> Fixing the statuses seems reasonable, but this seems like it's trying to establish a new process which isn't documented. These statuses do not change the process, they try to...

> If more "quickly merging" of PPCs is to be done, I would suggest finding an accepted mechanism for discussing active PPC proposals as currently the PR is the only...