Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114675
MIME-Version: 1.0
References: <CAOfzkkxbS6CQidg4-uai42PPRPHfWWL9UZTd+zDgspXsFSr5zg@mail.gmail.com>
 <CABAhh3ER9_Pv6g7jANQ-qoTE6DmTLHWTv6Ggjr+qvnbXqXBB0w@mail.gmail.com>
 <CANS-=pc0qe7aRLAPxSjj+AT46m8Y=ARB4L8AwESKmiQVK=dEJw@mail.gmail.com>
 <CABAhh3GfC+69FoGzUQxC+O3MhiETgN_s4edYQL2FUndrex5-JA@mail.gmail.com>
 <CAOfzkkxSw7euY_nhOVo+gHx8FXjycVey84j+YiEZMXpPAkvKmA@mail.gmail.com>
 <CABAhh3GwwmsyyFwbwN6OHFKCT1zkTdBmmKcCvSC=WxxAwyDh+A@mail.gmail.com>
 <CAG4FTXySSCV8io6kkgExAewj+DG2eGfm2r=Vg9Vr6t+M2xQx2A@mail.gmail.com>
 <PA4PR02MB68005CAC217AD3B0EAB5DCE7B8259@PA4PR02MB6800.eurprd02.prod.outlook.com>
 <E5A7BE78-D8E2-45AF-B2B4-40538DFEA57F@newclarity.net> <CAG4FTXyz-EkWPTbaBXaKLSFmaaidpLokuuzsg_FbMK0YwDEPEA@mail.gmail.com>
 <CD1CCD71-B0DE-48A5-A18F-E23E90B083F7@newclarity.net> <CAF+90c8RhWxKzUKfC4o29gC-nibf33m2qf+Nu4=zTRamLG6W8Q@mail.gmail.com>
 <60b13dc9.1c69fb81.39116.72e0SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <60b13dc9.1c69fb81.39116.72e0SMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 31 May 2021 12:02:21 +0200
Message-ID: <CAF+90c9+LN5OMCA-ZJmkw1-hucm2bHbzTWRg_sOFxrD+Lpp=-g@mail.gmail.com>
To: Mark Randall <marandall@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004147f905c39d53d4"
Subject: Re: [PHP-DEV] A little syntactic sugar on array_* function calls?
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000004147f905c39d53d4
Content-Type: text/plain; charset="UTF-8"

On Fri, May 28, 2021 at 9:00 PM Mark Randall <marandall@php.net> wrote:

> On 28/05/2021 15:31, Nikita Popov wrote:
> > This is a more complex case. In this case the compiler doesn't know in
> > advance whether the argument is passed by value or by reference. What
> > happens here is:
>
>
> I'm trying to wrap my head around this, but if a function arg can handle
> this, does something internal to the engine preclude fetching in write
> context, after already fetching in read context, other than performance?
>
> So can the initial fetch be performed with FETCH_DIM_R, handling the
> object case + any other scalars, and if and only if the value is an
> array and operating on what would traditionally be a by-ref, repeating
> the previous lookup with FETCH_DIM_W?
>

This is theoretically possible, in that this is exactly how $a[$b][$c] ??=
$d is implemented. Everything is first fetched as FETCH_DIM_IS and then
again as FETCH_DIM_W if an assignment is necessary. However, this does
require emitting both fetch sequences, with one guarded by a branch,
together with temporary copies to allow re-fetching without re-evaluating
side-effecting operands. Of course, it also has fun interactions with magic
ArrayAccess/__get, in which case both fetches may produce different
results. All this is something we can live with for the ??= operator, but
not for every single method call.

Regards,
Nikita

--0000000000004147f905c39d53d4--