Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130281
Precedence: list
MIME-Version: 1.0
References: <CAOWwgp=JtbTSVCv9z=QGx9yS=8G72L-hcAjcOj33eEMLB0zfvg@mail.gmail.com>
In-Reply-To: <CAOWwgp=JtbTSVCv9z=QGx9yS=8G72L-hcAjcOj33eEMLB0zfvg@mail.gmail.com>
Date: Mon, 9 Mar 2026 18:57:34 +0100
Message-ID: <CAOWwgpnXs2uTi2p6hpLTbsZK9J4XZtmA_f72hjKVJ+RrbUG4Aw@mail.gmail.com>
Subject: [PHP-DEV] Re: [RFC] Allow Reassignment of Promoted Readonly Properties in Constructor
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000dd6b86064c9b2302"
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000dd6b86064c9b2302
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le jeu. 22 janv. 2026 =C3=A0 16:33, Nicolas Grekas <nicolas.grekas+php@gmai=
l.com>
a =C3=A9crit :

> Dear all,
>
> Here is a new RFC for you to consider:
> https://wiki.php.net/rfc/promoted_readonly_constructor_reassign
>
> As a quick intro, my motivation for that RFC is that I find it quite
> annoying that readonly properties play badly with CPP (constructor proper=
ty
> promotion).
>
> Doing simple processing of any argument before assigning it to a readonly
> property forces opting out of CPP.
>
> This RFC would allow setting once a readonly property in the body of a
> constructor after the property was previously (and implicitly) set using
> CPP.
>
> This allows keeping property declarations in their compact form while
> still enabling validation, normalization, or conditional initialization.
>


Friendly reminder about this RFC. It's been quiet for 13 days so I plan to
start the vote on Thursday if there are no more concerns to the text of the
proposal.

Cheers,
Nicolas

--000000000000dd6b86064c9b2302
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0jeu. 22=
 janv. 2026 =C3=A0=C2=A016:33, Nicolas Grekas &lt;<a href=3D"mailto:nicolas=
.grekas%2Bphp@gmail.com">nicolas.grekas+php@gmail.com</a>&gt; a =C3=A9crit=
=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div>Dear all,</div><div><br></div><div>Here is a=C2=A0new RFC for=
 you to consider:</div><div><a href=3D"https://wiki.php.net/rfc/promoted_re=
adonly_constructor_reassign" target=3D"_blank">https://wiki.php.net/rfc/pro=
moted_readonly_constructor_reassign</a></div><div><br></div><div>As a quick=
 intro, my motivation for that RFC is that I find it quite annoying that re=
adonly properties play badly with CPP (constructor property promotion).</di=
v><div><br>Doing simple processing of any argument before assigning it to a=
 readonly property forces opting out of CPP.<br><br>This RFC would allow se=
tting once a readonly property in the body of a constructor after the prope=
rty was previously (and implicitly) set using CPP.<br><br></div>This allows=
 keeping property declarations in their compact form while still enabling v=
alidation, normalization, or conditional initialization.<br></div></blockqu=
ote><div><br></div><div><br></div><div>Friendly reminder about this RFC. It=
&#39;s been quiet for 13 days so I plan to start the vote on Thursday if th=
ere are no more concerns to the text of the proposal.</div><div><br></div><=
div>Cheers,</div><div>Nicolas</div></div></div>

--000000000000dd6b86064c9b2302--