Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128112
Message-ID: <93a7a354-9779-4c2d-a146-a49388bc0159@bastelstu.be>
Date: Fri, 18 Jul 2025 16:42:54 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Readonly property hooks
To: Faizan Akram Dar <hello@faizanakram.me>
Cc: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
References: <1e8634d7-ac1a-4025-b4e2-1948aabf5251@app.fastmail.com>
 <CAMzRQTdDNsF_LPpNKUbVROTWjDbN2uDw-j2PrL3xp7qASA62GA@mail.gmail.com>
 <be533915-2b0d-460d-a5ea-76fe98fc4080@app.fastmail.com>
 <f4e4057b19a5ed9de7ad92215e78d58c@bastelstu.be>
 <cedce076-82de-4391-8a03-409690added9@app.fastmail.com>
 <CAOWwgp=o0PpE2b8TD9reKvO053UAu5RxTaFA7g+Huu7GozxrhQ@mail.gmail.com>
 <46857A6D-5EAF-44AF-A2DE-9B40AF8DE8C8@gmail.com>
 <41241c3d-a601-4fb8-9f32-976bea3b660e@app.fastmail.com>
 <308e51e9-ebc9-4ab1-a727-46854b27701f@bastelstu.be>
 <CAMkukMxjTaebvr+wnqOBWbGhgxDiqNRsbNV+WepNoBmaeV9z0A@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAMkukMxjTaebvr+wnqOBWbGhgxDiqNRsbNV+WepNoBmaeV9z0A@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/18/25 16:25, Faizan Akram Dar wrote:
> The problem with allowing only set hooks is that readonly class won't be
> compatible with hooks, I think that is one of the main motivations behind
> this RFC.

Yes. The point is that the semantics users expect from `readonly` are 
fundamentally incompatible with a get hook that could return arbitrarily 
changing values whenever you read from a property.

Proposing to change this is like proposing an RFC that allows storing a 
`string` in a property with type `array`. It would be a massive break in 
user expectations for a feature that existed since 4 PHP versions (in 
case of readonly).

Best regards
Tim Düsterhus