Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123602
Precedence: bulk
MIME-Version: 1.0
References: <CAOWwgpmbq5VRrZQvUXDsKiNK4r6+bFA4VxnjQ_U=h8T9r0o3DA@mail.gmail.com>
 <ab83af79-0669-47dd-a3cb-ab72327ae174@bastelstu.be> <CAP1Jc13JWVg99AULgzrGXcoCWJtJZGz+nr_VoyUocw8n5n5sfQ@mail.gmail.com>
 <c77832b9-4143-43aa-a71b-eb9d888725e9@app.fastmail.com> <CAP1Jc12ZwcMS87D2f2r0NwyGJgWxbxEHMa_V7rc8Mjespavt+A@mail.gmail.com>
 <CABdc3WpGcToxMpRNPXe3Qcn4P6k7yL-2MMGQNjZhyrbYv2Fq3w@mail.gmail.com>
In-Reply-To: <CABdc3WpGcToxMpRNPXe3Qcn4P6k7yL-2MMGQNjZhyrbYv2Fq3w@mail.gmail.com>
Date: Fri, 14 Jun 2024 15:03:30 +0200
Message-ID: <CAP1Jc10+pNpPTYCR-+PTh6CvfpSh3SoQTWCbSaiTye4WFzfE5g@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: =?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?= <michal.brzuchalski@gmail.com>, 
	Chris Riley <t.carnage@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <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 Micha=C5=82, Chris,

On Thu, Jun 6, 2024 at 8:53=E2=80=AFAM Micha=C5=82 Marcin Brzuchalski
<michal.brzuchalski@gmail.com> wrote:
> Did you consider implementing it using some attribute?

On Sun, Jun 9, 2024 at 1:24=E2=80=AFAM Chris Riley <t.carnage@gmail.com> wr=
ote:
> I'm wondering why this has been attached to the existing reflection API i=
nstead of being a new thing in and of itself? It doesn't seem strictly rela=
ted to reflection other than currently the solutions for this rely on refle=
ction to work.

Thank you for your feedback.

Currently the lazy objects feature is designed as a low-level
technical building block that libraries and frameworks can use. FFI
and Fibers are examples of such features that most users do not use
directly, but can benefit greatly from within libraries they use.

We have considered the proposed syntaxes, such as using annotations,
but these do not match the core use case of creating a lazy instance
of a class without requiring cooperation from the class itself.
Furthermore we believe that designing a higher-level API in the
language would be considerably more difficult and could put the RFC at
risk.

However, it is possible to introduce a higher-level way to create lazy
objects in a future RFC.

Best Regards,
Arnaud