Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130430
Precedence: list
MIME-Version: 1.0
References: <CAOWwgpku3D2mvADw8+9=zNsDFZfjzZOFODM6aR0O44Zj9gBXxQ@mail.gmail.com>
In-Reply-To: <CAOWwgpku3D2mvADw8+9=zNsDFZfjzZOFODM6aR0O44Zj9gBXxQ@mail.gmail.com>
Date: Tue, 24 Mar 2026 12:52:10 +0100
Message-ID: <CAPyj-LDaBRnLgtp0y66i8_7i3se+D7tz4gOJoi=z1CQDZQV8iA@mail.gmail.com>
Subject: Re: [PHP-DEV] [VOTE] Allow Reassignment of Promoted Readonly
 Properties in Constructor
To: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Nicolas

On Mon, Mar 23, 2026 at 4:39=E2=80=AFPM Nicolas Grekas
<nicolas.grekas+php@gmail.com> wrote:
>
> It's now time to open the vote for the following RFC:
> https://wiki.php.net/rfc/promoted_readonly_constructor_reassign
>
> The vote will close on 2026-04-07 at 16:00 UTC.

I voted "no" because I think the property logic, especially readonly,
is already too convoluted. We've already had to deploy multiple fixes
to make it workable (those being unlocking during __clone, and clone()
with). In my opinion, if you need to modify a property during
construction, there's already private(set), for which local mutability
is easy to restrict.

Nonetheless, thanks for the RFC and thanks for entertaining my ideas
for the technical changes.

Ilija