Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124454
Precedence: bulk
MIME-Version: 1.0
References: <5bdbffef-4954-415d-9dae-4c9bd4ba0f22@scriptfusion.com>
 <CAKVXxD_=0=P2uCgSmkA-6pN3E-Gm-rwKL6S-C066+xJt+qzmSg@mail.gmail.com> <CANNiG7he8iVZPTZMR4vBpn8BY=mUFrbgu7X00PgQFjNqCgpZPA@mail.gmail.com>
In-Reply-To: <CANNiG7he8iVZPTZMR4vBpn8BY=mUFrbgu7X00PgQFjNqCgpZPA@mail.gmail.com>
Reply-To: lilybergonzat+php@gmail.com
Date: Wed, 17 Jul 2024 09:55:20 +0200
Message-ID: <CAPPUTHqP+93yW=Kp5raTDvV37P1NH8p2yHtUbVe9sRzhGB1eaQ@mail.gmail.com>
Subject: Re: [PHP-DEV] array_reduce callback key
To: Bilge <bilge@scriptfusion.com>
Cc: mickmackusa <mickmackusa@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: lilybergonzat+php@gmail.com (Lily Bergonzat)

While it *is* indeed a workaround, you can very easily
access the values of the array from the keys, since that
literally is what the keys are for.

While I also think it's weird that not all php array functions
with callbacks do pass the key as an argument, and while
I also stumbled upon that problem in the past myself
multiple times, I also think it is worth taking the time to
consider what other people from this mailing list are
bringing up. If it could indeed break internal callbacks,
then I think using the workaround could be a better idea
than potentially breaking other things.

On Wed, Jul 17, 2024 at 2:38=E2=80=AFAM Bilge <bilge@scriptfusion.com> wrot=
e:
>
> On Wed, 17 Jul 2024, 01:29 mickmackusa, <mickmackusa@gmail.com> wrote:
>>
>> It is untrue that you "can't access it"; you just need to use an array o=
f keys as the input array.
>
> It is absolutely true and your workaround is just that; a workaround that=
 doesn't work at all when you also need the value.
>
> Cheers,
> Bilge