Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100474
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.216.195 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <1504883189.2374.26.camel@schlueters.de>
References: <CAEsg9X0mUWuLjGEPuWF6w7m-PNG1V_WHRa8TSvs5L0pz1kgJ+A@mail.gmail.com>
 <1504883189.2374.26.camel@schlueters.de>
Date: Fri, 8 Sep 2017 11:17:08 -0700
Message-ID: <CAESVnVqSTX=j_6ow=Pu+ALtg2fcZDRVaQSjGzwUqVH76z6Wn+Q@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: David Rodrigues <david.proweb@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] array_filter vs for/foreach usage cost
From: pollita@php.net (Sara Golemon)

On Fri, Sep 8, 2017 at 8:06 AM, Johannes Schl=C3=BCter
<johannes@schlueters.de> wrote:
> On Do, 2017-09-07 at 15:13 -0300, David Rodrigues wrote:
>> I understand that array_filter() should costs more than for/foreach
>> because
>> it is a function call that call another function for each item, while
>> the
>> for/foreach is a language constructor that works on a way totally
>> different
>> and its optimized for this kind of job.
>
> The main cost in that is that array_filter has to create a copy of the
> array. An alternative is using an FilterIterator or generator or such
> which would make this a pipeline step. (with iterators there are
> multiple function calls, while the function descriptor is cached,
> making them relatively cheap) I'd focus on improving those.
>
*cough*
https://github.com/phplang/generator/blob/master/src/iterable.php#L64
*cough*

-Sara