Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102878
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain web.de designates 212.227.15.3 as permitted sender)
To: Zeev Suraski <zeev@zend.com>, Levi Morrison <levim@php.net>
Cc: internals <internals@lists.php.net>
References: <CAFMT4NqPobFGvkcZ7nxaGHtpQsa+TOvdp13Ebab_6hH_859TCQ@mail.gmail.com>
 <1A9B9639-2425-450D-81EE-81059E725617@zend.com>
Message-ID: <6ea65c16-2b31-173a-cfb8-afdadd3c3428@web.de>
Date: Tue, 17 Jul 2018 08:23:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1A9B9639-2425-450D-81EE-81059E725617@zend.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Replacing array_slice
From: enno.woortmann@web.de (Enno Woortmann)

Am 17.07.2018 um 07:35 schrieb Zeev Suraski:
>> On 17 Jul 2018, at 7:12, Levi Morrison <levim@php.net> wrote:
>>
>> Fixing `array_slice` would probably do more harm than good at this
>> stage. Instead I would like to provide an alternative function that
>> does not have all this baggage, and will have decent performance much
>> of the time. The best ideas I have for names are not that great:
>>
>>   - `array_real_slice`?
>>   - `array_slice2`?
> array_carve()?  array_chisel()?
>
> Zeev
>

If keeping it together in a single function maybe array_extract() will 
do the job.
Or do you think it's to close to the naming of extract() and may lead to 
confusion?

Enno