Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123939
Precedence: bulk
MIME-Version: 1.0
References: <CAOWwgpmbq5VRrZQvUXDsKiNK4r6+bFA4VxnjQ_U=h8T9r0o3DA@mail.gmail.com>
 <28781fd3-82ac-4c69-88a1-3ead4f0081b9@app.fastmail.com>
In-Reply-To: <28781fd3-82ac-4c69-88a1-3ead4f0081b9@app.fastmail.com>
Date: Thu, 27 Jun 2024 16:32:22 +0200
Message-ID: <CAP1Jc13=kRhJw=FWR23nE_EDyjC6Pf2RkwR8=NYgXJ9NxnSyBg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: Rob Landers <rob@bottled.codes>
Cc: 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 Rob,

On Wed, Jun 26, 2024 at 11:09=E2=80=AFPM Rob Landers <rob@bottled.codes> wr=
ote:
> Can you add to the RFC how to proxy final classes as well? This is mentio=
ned (unless I misunderstood) but in the proxy example it shows the proxy cl=
ass extending the proxied class (which I think is an error if the base clas=
s is final). How would this work? Or would it need to implement a shared in=
terface (this is totally fine IMHO)?

The example you are referring to in the "About Proxies" section is a
digression about how the lazy-loading inheritance-proxy pattern could
be achieved on top of the lazy-loading state-proxy pattern implemented
by this RFC, but it doesn't represent the main use-case.

To proxy a final class with this RFC, you can simply call the
newLazyProxy method:

final class MyClass {
    public $a;
}

$reflector =3D new ReflectionClass(MyClass::class);
$obj =3D $reflector->newLazyProxy(function () {
    return new MyClass();
});

Best Regards,
Arnaud