Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124436
Message-ID: <2a0a4650-c2c5-4c6d-ad3a-25365b3391b2@bastelstu.be>
Date: Mon, 15 Jul 2024 21:42:03 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>,
 Rob Landers <rob@bottled.codes>
Cc: =?UTF-8?Q?Benjamin_Au=C3=9Fenhofer?= <kontakt@beberlei.de>,
 PHP Internals List <internals@lists.php.net>
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>
Content-Language: en-US
In-Reply-To: <CAOWwgpngQtg2NRW6M6RwgSH+OS1iipewHBmM5c36P2MxQGX78A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 7/15/24 09:25, Nicolas Grekas wrote:
> Testing is actually a good domain where resetting lazy objects might open
> interesting use cases.
> This reminded me about zenstruck/foundry, which leverages the
> LazyProxyTrait to provide refreshable fixture objects
> <https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#auto-refresh>
> and provides nice DX thanks to this capability.
> 

I have not used this library before, but I have taken a (very) brief 
look at the code and documentation.

My understanding is that all the fixture objects are generated by a 
corresponding Factory class. This factory clearly has the capability of 
constructing objects by itself, so it could just create a lazy proxy 
instead?

I'm seeing the `instantiateWith()` example in the documentation where 
the user can return a constructed object themselves, but I'm not seeing 
how that can safely be combined with the `reset*()` methods: Anything 
special the user did to construct the object would be reverted, so the 
user might as well rely on the default construction logic of the factory 
then.

What am I missing?

Best regards
Tim Düsterhus