Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108685
User-Agent: Cyrus-JMAP/3.1.7-802-g7a41c81-fmstable-20200203v1
Mime-Version: 1.0
Message-ID: <65c78b5a-55a6-4f1f-b881-f1401aa7dbb1@www.fastmail.com>
In-Reply-To: 
 <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
References: 
 <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
Date: Wed, 19 Feb 2020 12:50:42 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Immutable/final/readonly properties
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, Feb 19, 2020, at 11:05 AM, M=C3=A1t=C3=A9 Kocsis wrote:
> Hi Internals,
>=20
> I'd like to move my RFC forward to the discussion phase:
> https://wiki.php.net/rfc/write_once_properties
>=20
> In short, I propose to add support for a new property modifier that wo=
uld
> allow properties to be initialized, but not modified afterwards.
>=20
> Cheers,
> M=C3=A1t=C3=A9 Kocsis

As envisoned, does this allow for a property to be set to a dynamic valu=
e?  My concern is that while a public locked/writeonce property is great=
 for access, it doesn't do anything to enable lazy setting on first acce=
ss.  In fact the only way to do that would be to make it private and wra=
p access in a method, which would look exactly like that does now but wi=
th an extra keyword that doesn't actually offer much.

You could set the value in advance in the constructor, but then it's not=
 lazy, just locked.

Is there a way it could support lazy-on-first-use then locked?

--Larry Garfield