Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96657
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
To: internals@lists.php.net
References: <44244cfd-c8ad-e0a9-4e70-380a8a8c940c@syberisle.net>
 <CAFMT4Nr+d1k20aY0P9o1G9KU_C9wz2cg2UOPrbE3qbXDBhqe3w@mail.gmail.com>
 <CAF+90c_7g_YdxTfUX8t_OifVJTL=OcvjsC_smWc95M-CcRYaNw@mail.gmail.com>
 <CADqTB_jN6RQxEP5tAJY4T+kuv_rkTzRNvL9T1j-iVX5LG5H3Gg@mail.gmail.com>
 <CAF+90c_rE7DiJ8KEYzFO9GHqx56rin+CiByPe7hRF0fUm-zKBQ@mail.gmail.com>
 <01f2f3da-592b-fd23-709d-ad620422f56d@fleshgrinder.com>
Message-ID: <7fb9a5d5-318d-7ed3-59eb-d9845ed5dec1@gmail.com>
Date: Sun, 30 Oct 2016 17:19:24 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <01f2f3da-592b-fd23-709d-ad620422f56d@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Allow Iterator to be used with current, next, reset,
 key functions
From: rowan.collins@gmail.com (Rowan Collins)

On 30/10/2016 12:07, Fleshgrinder wrote:
> I think it makes much more sense to deprecate all of them and introduce
> new ones that work in the way we want them to for several reasons.
> `end()` and `reset()` would have to continue working as they do until
> the next major release since people who use them might rely on the way
> they work. This means in effect that nobody can make her PHP 7 code PHP
> 8 ready up front.
>
> Instead we could directly introduce `array_first()` and `array_last()`
> with the next feature release -- even if the others are not deprecated
> -- and everyone can update their code or at least use it in new code.

I've always felt like these functions were "missing" from the language - 
there are a number of ways you *can* get the first or last item in an 
array, but all have side effects, because they're not designed for this 
purpose. It just so happens that - most of the time - reset() and end() 
have the smallest side effects.

I can't remember if it was an earlier discussion here, or somewhere 
else, that pointed to getting the first and last *key* as an extra use 
case worth considering. It's currently possible (if awkward) with key().

I think it would make sense to, in the same version:

- deprecate reset(), end(), each(), and key()
- introduce array_first(), array_last(), array_first_key() and 
array_last_key()
- document replacements for whatever other use cases we can find examples of

Doing them all at once makes the messaging much clearer - this family of 
functions is going to be removed; and here are the new functions you can 
start using immediately instead.

Regards,

-- 
Rowan Collins
[IMSoP]