Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116472
MIME-Version: 1.0
Date: Mon, 22 Nov 2021 17:13:49 +0100
Message-ID: <CAH5C8xUn9fD5=hkKQL+CMWSMXEugpX=HbSRcWQ3WTksCpXdt_A@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a9525f05d162e913"
Subject: [RFC] [Discussion] Readonly Classes
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--000000000000a9525f05d162e913
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Internals,

I'd like to propose adding support for readonly classes:
https://wiki.php.net/rfc/readonly_classes

The implementation heavily builds on the semantics of the already accepted
readonly properties RFC (https://wiki.php.net/rfc/readonly_properties_v2),
basically the only thing I had to implement in the PR are the following:
- Any declared property of a readonly class is implicitly treated as
readonly
- Creation of dynamic properties is forbidden

Readonly classes would make it easier to declare immutable(-alike) classes,
especially if a class
contains a lot of properties. As a side-effect, one could already opt out
from dynamic properties
completely, which won't really be possible for quite some time, even if
https://wiki.php.net/rfc/deprecate_dynamic_properties passes.

Regards:
M=C3=A1t=C3=A9

--000000000000a9525f05d162e913--