Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127626
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sun, 08 Jun 2025 20:10:10 +0200
To: internals@lists.php.net
Message-ID: <30a02845-8bf5-421e-af1c-9cac3559ac1f@app.fastmail.com>
Subject: [PHP-DEV] static properties in readonly classes
Content-Type: multipart/alternative;
 boundary=3124c6e132bf4b91a2ec658ec0bb9b8e
From: rob@bottled.codes ("Rob Landers")

--3124c6e132bf4b91a2ec658ec0bb9b8e
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello internals,

As far as I can tell from previous conversations and PRs; static propert=
ies aren=E2=80=99t supported in readonly classes for technical reasons a=
nd because nobody was sure what to do with them ...=20

... but that seems weird because you can also do something like this: ht=
tps://3v4l.org/uYNQD to hack your way around it if you want a mutable st=
atic state encapsulated in the class.

So, I would like to propose a question: should readonly classes be allow=
ed to have static properties? And if so, should they be allowed to be mu=
table? Or rather, should the static keyword also be prevented from being=
 used in readonly class methods?

It just feels weird to say that "static properties aren=E2=80=99t allowe=
d, but you can create static properties by embedding them in a method!" =
In other words, it feels inconsistent.

=E2=80=94 Rob
--3124c6e132bf4b91a2ec658ec0bb9b8e
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>Hello intern=
als,</div><div><br></div><div>As far as I can tell from previous convers=
ations and PRs; static properties aren=E2=80=99t supported in readonly c=
lasses for technical reasons and because nobody was sure what to do with=
 them ... </div><div><br></div><div>... but that seems weird because you=
 can also do something like this:&nbsp;<a href=3D"https://3v4l.org/uYNQD=
">https://3v4l.org/uYNQD</a>&nbsp;to hack your way around it if you want=
 a mutable static state encapsulated in the class.</div><div><br></div><=
div>So, I would like to propose a question: should readonly classes be a=
llowed to have static properties? And if so, should they be allowed to b=
e mutable? Or rather, should the static keyword also be prevented from b=
eing used in readonly class methods?</div><div><br></div><div>It just fe=
els weird to say that "static properties aren=E2=80=99t allowed, but you=
 can create static properties by embedding them in a method!" In other w=
ords, it feels inconsistent.</div><div><br></div><div id=3D"sig121229152=
">=E2=80=94 Rob</div></body></html>
--3124c6e132bf4b91a2ec658ec0bb9b8e--