Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124575
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>
 <1118bbcd-a7b4-47bf-bf35-1a36ab4628e1@bastelstu.be> <CAP1Jc11vNiazMRL8Y-4NcJhsEkg6kgFNKLymTGfEPYRv114oTA@mail.gmail.com>
 <45847b93-02bf-459f-bcd2-81ba35a12c24@bastelstu.be> <CAOWwgpnt77-Sybzc3hcnFEui9t8wAv03NAov4xCK9ib_VRZ0JA@mail.gmail.com>
 <46bd4098-2936-4e46-98e9-fe55118325c2@bastelstu.be> <CAOWwgpkCy++W1C2t0PnkZ71S8vq1B734ZNPGw2-OHjmrwO3L4A@mail.gmail.com>
 <61ab36bc-b045-452a-84e0-87367d4c680e@bastelstu.be> <CAEPJduk6m1gdPOrsXYbsc+RLuHeEBav3pGwQO+PHs4UGGqtzhg@mail.gmail.com>
 <07e065f2-8f64-4bad-9a98-51f4eaf63ddb@app.fastmail.com> <CAOWwgpngQtg2NRW6M6RwgSH+OS1iipewHBmM5c36P2MxQGX78A@mail.gmail.com>
 <2a0a4650-c2c5-4c6d-ad3a-25365b3391b2@bastelstu.be> <CAOWwgpm9FLy_SNt7HLtJh5sxtfwjZMMN6pOKioDqsJc+GgD-sA@mail.gmail.com>
 <CAOWwgpnwoPH_rkJreh8v+X8WagzcCJ_puT1RWC0c717GMj5Onw@mail.gmail.com>
 <CAOWwgp=uwDebrx-=H8yP1Dgwf9ji=v_qagw9aAxbDJcPvCqKNw@mail.gmail.com>
 <b096b1d3-4414-4b53-a3b0-3a87c8dd7ff3@app.fastmail.com> <CAOWwgp=88jWSR-roWTrkkgwVgQvLQYbkTGSGAr6ASPs6s7s_4g@mail.gmail.com>
 <2fd6d80d-a55c-4aad-aeee-6d07d4b930a1@app.fastmail.com>
In-Reply-To: <2fd6d80d-a55c-4aad-aeee-6d07d4b930a1@app.fastmail.com>
Date: Wed, 24 Jul 2024 16:28:01 +0200
Message-ID: <CAOWwgp=zu8y95EyEvjidNuiBOr8-ckek_xFmrcA_JifLy3U2Xg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: Larry Garfield <larry@garfieldtech.com>, Rob Landers <rob@bottled.codes>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000bb13b9061dff1617"
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000bb13b9061dff1617
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le mer. 24 juil. 2024 =C3=A0 16:05, Larry Garfield <larry@garfieldtech.com>=
 a
=C3=A9crit :

> On Thu, Jul 18, 2024, at 7:12 AM, Nicolas Grekas wrote:
>
> >> Otherwise, I'm quite looking forward to this.
> >
> > =F0=9F=A4=9E
>
> Another thought that occurred to me.  Given how lightweight it *looks* to
> be (may not actually be, but looks it), how much overhead would there be =
to
> having a compiled DI container that is lazy by default?  Just make
> everything lazy with a fairly standard initializer or factory, unless a
> specific case says you shouldn't.  That way you can use optional
> dependencies in a constructor pretty much at will with no overhead of
> needing to create a chain of dependencies as a result.
>
> Would that be a bad idea for some reason, or would it actually work?
>
> (This doesn't really affect my vote, more just a thought that came up.)


I see no blockers.

I don't have numbers nor plan to play with this idea in the short term but
that could be fun to try :)
Eg the Symfony DI could be updated to leverage the new mechanism (I did it
already with a previous version of the RFC) and we'd try running an app
with all services defined as lazy by default.

To Rob: proxying by interface can be implemented using regular code
generation so it's not a blocker. Symfony does it already, and will
continue to do it to cover the use case.

Nicolas

--000000000000bb13b9061dff1617
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0mer. 24 juil. 2024 =C3=A0=C2=
=A016:05, Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larr=
y@garfieldtech.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Thu, Jul 18, 2024, at 7:12 AM, Nicolas =
Grekas wrote:<br>
<br>
&gt;&gt; Otherwise, I&#39;m quite looking forward to this.<br>
&gt;<br>
&gt; =F0=9F=A4=9E<br>
<br>
Another thought that occurred to me.=C2=A0 Given how lightweight it *looks*=
 to be (may not actually be, but looks it), how much overhead would there b=
e to having a compiled DI container that is lazy by default?=C2=A0 Just mak=
e everything lazy with a fairly standard initializer or factory, unless a s=
pecific case says you shouldn&#39;t.=C2=A0 That way you can use optional de=
pendencies in a constructor pretty much at will with no overhead of needing=
 to create a chain of dependencies as a result.<br>
<br>
Would that be a bad idea for some reason, or would it actually work?<br>
<br>
(This doesn&#39;t really affect my vote, more just a thought that came up.)=
</blockquote><div><br></div><div>I see no blockers.</div><div><br></div><di=
v>I don&#39;t have numbers nor plan to play with this idea in the short ter=
m but that could be fun to try :)</div><div>Eg the Symfony DI could be upda=
ted to leverage the new mechanism (I did it already with a previous version=
 of the RFC) and we&#39;d try running an app with all services defined as l=
azy by default.</div><div><br></div><div>To Rob: proxying by interface can =
be implemented using regular code generation so it&#39;s not a blocker. Sym=
fony does it already, and will continue to do it to cover the use case.</di=
v><div><br></div><div>Nicolas<br></div></div></div>

--000000000000bb13b9061dff1617--