Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123525
Message-ID: <91795c9f-d6e1-4090-afb3-34c197df6e7c@bastelstu.be>
Date: Wed, 5 Jun 2024 20:35:36 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Lazy Objects
To: Arnaud Le Blanc <arnaud.lb@gmail.com>,
 Larry Garfield <larry@garfieldtech.com>
Cc: php internals <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>
 <c77832b9-4143-43aa-a71b-eb9d888725e9@app.fastmail.com>
 <CAP1Jc12ZwcMS87D2f2r0NwyGJgWxbxEHMa_V7rc8Mjespavt+A@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAP1Jc12ZwcMS87D2f2r0NwyGJgWxbxEHMa_V7rc8Mjespavt+A@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

Thank you Larry for your email. Your suggested API is basically what I 
also had in mind after Arnaud's clarification.

On 6/5/24 20:06, Arnaud Le Blanc wrote:
> I think you got the two strategies right. However, there is a use-case
> in which an object manages its own laziness by making itself lazy:

What is the corresponding real-world use case for that? When would I 
want to create an object that makes itself lazy?

FWIW: If I understand it right, this use case would be supported by 
Larry's proposed API by writing a named constructor:

     class C {
       private function __construct($foo, $bar) { }
       public static function lazyNew(...$args) {
         $r = new ReflectionClass(self::class);

         return $r->newInstanceWithLazyConstructor(fn ($o) => 
$o->__construct(...$args));
       }
     }

>> It also suggests that perhaps the function should be using $this, not $foo, as it's running within the context of the object (I presume?  Can it call private methods?  I assume so since it can set private properties.)
> 
> The function is not running in the context of the object. It can only
> access private members via Reflection or if the closure was bound to
> the right scope by the user. This should not be an issue when the
> initializer just calls a public constructor.

Please clarify the interaction with visibility in the RFC.

Best regards
Tim Düsterhus