Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127613
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 05 Jun 2025 12:06:35 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <6b12585d-199f-4dc6-a557-5e68f59841b7@app.fastmail.com>
In-Reply-To: <3FBC491A-FE60-4583-A3A2-0A58EC384C88@nicksdot.dev>
References: <B0250A18-3C43-4DFD-9D99-3391C23D9D65@nicksdot.dev>
 <3FBC491A-FE60-4583-A3A2-0A58EC384C88@nicksdot.dev>
Subject: Re: [PHP-DEV] Allow hooks in `readonly` promoted properties
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, Jun 5, 2025, at 1:12 AM, Nick wrote:
> Hey internals,
>
>> On 4. Jun 2025, at 20:19, Nick <php@nicksdot.dev> wrote:
>>> I believe at the moment that RFC text is all there is. :-)  I don't =
know that it's worth opening a discussion without at least a mostly-done=
 implementation.  Also, Ilija is rather busy on other tasks at the momen=
t, as am I.  (Unless someone else wants to jump in to implement it, whic=
h would be fine.)
>>=20
>> People often say =E2=80=9Cyou can just do things=E2=80=9D. So I did, =
and tried to contribute the code for your existing RFC text:
>>=20
>> https://github.com/php/php-src/pull/18757
>
> Would this be expected to work? Can interface properties be declared `=
readonly`?
> interface Cleaned
> {
>     public readonly string $clean { get; } // has readonly
> }

Interface properties cannot be declared readonly today:

https://3v4l.org/cXgR0

Which I think is correct behavior.

Make sure to include a test based on the "lazy product" example from the=
 RFC text.  That's the main sort of use case I'd expect we'd want to ena=
ble. :-)

--Larry Garfield