Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123940
Precedence: bulk
MIME-Version: 1.0
References: <CAOWwgpmbq5VRrZQvUXDsKiNK4r6+bFA4VxnjQ_U=h8T9r0o3DA@mail.gmail.com>
 <CAAKU0u=NL22QO_ii76NGxEFv8_RtpLy9N0Oku0gBztA0u2vrXA@mail.gmail.com>
 <CAP1Jc10=qZQyg9Qi9WWo1pAbmnMJZL-=-dpWJ_XDyJEYQoecvA@mail.gmail.com> <CADyq6sLAC5Tme78gGRB-Ti3GfcFCmU9hp9iM2iGdVBO4Mhg+=g@mail.gmail.com>
In-Reply-To: <CADyq6sLAC5Tme78gGRB-Ti3GfcFCmU9hp9iM2iGdVBO4Mhg+=g@mail.gmail.com>
Date: Thu, 27 Jun 2024 16:37:55 +0200
Message-ID: <CAP1Jc12pRrK9V91s50c+F1hjzDZtX3uwv0CDM-4zWT64M14YTg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: Marco Pivetta <ocramius@gmail.com>
Cc: Levi Morrison <levi.morrison@datadoghq.com>, 
	Nicolas Grekas <nicolas.grekas+php@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: arnaud.lb@gmail.com (Arnaud Le Blanc)

Hi Marco,

On Thu, Jun 27, 2024 at 12:32=E2=80=AFPM Marco Pivetta <ocramius@gmail.com>=
 wrote:
>
> Hey Arnaud,
>
> On Wed, 26 Jun 2024 at 21:06, Arnaud Le Blanc <arnaud.lb@gmail.com> wrote=
:
>>
>> The proposed implementation is adding very little complexity as it's not=
 adding any special case outside of object handlers (except in json_encode(=
) and serialize() because these functions trade abstractions for speed). Fu=
rthermore all operations that may trigger an object initialization are alre=
ady effectful, due to magic methods or hooks (so we are not making pure ope=
rations effectful). This means that we do not have to worry about lazy obje=
cts or to be aware of them anywhere in the code base, outside of object han=
dlers.
>>
>> To give you an idea, it's implemented by hooking into the code path that=
 handles accesses to undefined properties. This code path may call __get or=
 __set methods if any, or trigger errors, and with this proposal, may trigg=
er the initialization. Userland implementations achieve this functionality =
in a very similar way (with unset() and a generated sub-class with magic me=
thods), but they have considerably more edge cases to handle due to being a=
t a different abstraction level.
>
>
> Assuming this won't pass a vote (I hope it does, but I want to be optimis=
tic): is this something that could be implemented in an extension, or is it=
 only feasible in core?

An extension could achieve similar behavior by decorating the default
object handlers. However, it may have to re-implement a significant
part of the object handlers logic, so that initialization is triggered
at the right time.

Best Regards,
Arnaud