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,
> >
On 10/01/2021 16:52, tyson andre wrote:
- no namespace: iterable_any()/iterable_all()
- iter\ (conflicts with nikic/iter but was also suggested by Nikita)
- iterable\ (see below note)
- PHP\ (This deliberately uses uppercase, see
https://www.php.net/manual/en/language.namespaces.rationale.php)
I want to make a case for `Spl`. Aside from autoloading (which really
ought to be in core but since "spl" is literally in the name of those
functions it's kind of stuck), the SPL is mostly data structures and
iterator related functionality. It makes perfect sense to me that
iterator related
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
On 06/01/2021 14:57, Nikita Popov wrote:
Once you introduce an
additional meaningful namespace in the form of SPL\iterable\any, you are
better off either dropping the SPL part and arriving at iterable\any, or
replacing SPL with something more sensible and arriving at PHP\iterable\any.
On Wed, Jan 6, 2021 at 3:40 PM Levi Morrison
wrote:
> On Wed, Jan 6, 2021 at 1:55 AM Nikita Popov wrote:
> >
> > On Wed, Jan 6, 2021 at 2:28 AM tyson andre
> > wrote:
> >
> > > Hi internals,
> > >
> > > > I've created a straw poll for the naming pattern to use for `*any()`
> and
> > > `*all()`
On Wed, Jan 6, 2021 at 7:39 AM Levi Morrison
wrote:
>
> On Wed, Jan 6, 2021 at 1:55 AM Nikita Popov wrote:
> >
> > On Wed, Jan 6, 2021 at 2:28 AM tyson andre
> > wrote:
> >
> > > Hi internals,
> > >
> > > > I've created a straw poll for the naming pattern to use for `*any()` and
> > > `*all()`
On Wed, Jan 6, 2021 at 1:55 AM Nikita Popov wrote:
>
> On Wed, Jan 6, 2021 at 2:28 AM tyson andre
> wrote:
>
> > Hi internals,
> >
> > > I've created a straw poll for the naming pattern to use for `*any()` and
> > `*all()` on iterables.
> > >
On Wed, Jan 6, 2021 at 2:28 AM tyson andre
wrote:
> 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
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
On Sun, Dec 20, 2020, at 5:56 PM, tyson andre wrote:
> Hi Mark Randall,
>
> > These functions make sense. However I think we need to give renewed
> > consideration to:
> >
> > $itr->all();
> > $itr->some(...);
>
> That wouldn't help for arrays, which would be the most common use case
> - I
Hi Mark Randall,
> These functions make sense. However I think we need to give renewed
> consideration to:
>
> $itr->all();
> $itr->some(...);
That wouldn't help for arrays, which would be the most common use case - I
don't remember seeing an RFC for https://github.com/nikic/scalar_objects
On 19/12/2020 20:24, tyson andre wrote:
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
These functions make sense. However I think we need to give renewed
consideration to:
13 matches
Mail list logo
