Re: Straw poll: Naming for `*any()` and `*all()` on iterables

Hi internals, > I've created a straw poll for the naming pattern to use for > *any() and *all() on iterables. > https://wiki.php.net/rfc/any_all_on_iterable_straw_poll > > Background: The RFC > https://wiki.php.net/rfc/any_all_on_iterable proposes adding only > two functions, > but more functionality acting on iterables (array|Traversable) may be added in the future, > making it important to get feedback what people feel the best choice of naming pattern would be > to avoid inconsistency or name changes later on. > (Many alternatives were suggested in the initial RFC announcement - > https://externals.io/message/111756) I've received more feedback than I expected from voters that were strongly or moderately in favor of putting new categories of functionality in namespaces. I've started a different straw poll and plan to start voting on that on the 8th (this will be the last straw poll for iterable function naming for this RFC) https://wiki.php.net/rfc/any_all_on_iterable_straw_poll_namespace 1. I plan to propose additional internal functions for working with iterables if this succeeds, and would want to be sure this is the best name choice instead of just an acceptable name choice going forwards. 2. Additionally, this has been an opportunity for measuring overall interest in adopting namespaces for brand new categories of functionality. It can be argued that this is a new category of functionality because existing methods work on Traversables (iterator_*) or arrays (array_*), but generally not both. (classes such as https://www.php.net/manual/en/class.ffi-cdata.php have adopted namespaces, but no global functions in php-src that I'm aware of have adopted namespaces yet) Thanks, - Tyson