Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100472
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 84.19.169.162 cause and error)
Message-ID: <1504883189.2374.26.camel@schlueters.de>
To: David Rodrigues <david.proweb@gmail.com>, PHP Internals
	 <internals@lists.php.net>
Date: Fri, 08 Sep 2017 17:06:29 +0200
In-Reply-To: <CAEsg9X0mUWuLjGEPuWF6w7m-PNG1V_WHRa8TSvs5L0pz1kgJ+A@mail.gmail.com>
References: 
	<CAEsg9X0mUWuLjGEPuWF6w7m-PNG1V_WHRa8TSvs5L0pz1kgJ+A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] array_filter vs for/foreach usage cost
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

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.

johannes