Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129779
Message-ID: <dcee998d-4727-46a2-ba3c-03e71863ef3e@bastelstu.be>
Date: Sun, 18 Jan 2026 13:28:22 +0100
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [php-src] PR #20903: GH-10497 (const obj->prop write) -
 language change notes
To: Khaled Alam <khaledalam.net@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAJS5taANCzu9W+mzEd0-nE0hh22Jbb170jK7n2yBHjh7yj-gdA@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAJS5taANCzu9W+mzEd0-nE0hh22Jbb170jK7n2yBHjh7yj-gdA@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 1/15/26 07:36, Khaled Alam wrote:
>     A potentially surprising case: some newly-valid writes can be a no-op
>     when they target a temporary const value, e.g.
>     - const X = [1,2,3];  X[] = 4;
>        - const Y = ['a' => 1];  Y['b'] = 2;
> 
> These become valid syntax but have no effect because the write happens on a
> temporary basis.
> 
> Feedback on semantics + expected behavior for the temporary-write case is
> appreciated.

This is too unexpected / error-prone for me. Trying to write into arrays 
should remain disallowed / an Error, since this is never (?) useful.

For objects, I don't have a strong opinion, but I expect objects in 
constants to be so rare that it probably isn't worth it to make a change 
at all.

Best regards
Tim Düsterhus