Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119015
Date: Tue, 15 Nov 2022 23:06:30 +0000
CC: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CAH5C8xWmyLTv2DwX2a-f70kDJr4iysk6NZQqxMS1+aZzdgWvAA@mail.gmail.com>
References: <CAH5C8xUd4ueJ62pR6vT2haz9rFgrgspJQui1rPCqTneupD+tsQ@mail.gmail.com> <acd8b573-13af-7631-2ef1-3329226810bc@gmail.com> <CAH5C8xWmyLTv2DwX2a-f70kDJr4iysk6NZQqxMS1+aZzdgWvAA@mail.gmail.com>
Message-ID: <E7E4D654-88A5-4C84-B8D7-07FA591A4BF9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Discussion] Readonly class amendments
From: rowan.collins@gmail.com (Rowan Tommins)

On 15 November 2022 19:23:44 GMT, "M=C3=A1t=C3=A9 Kocsis" <kocsismate90@gma=
il=2Ecom> wrote:
>I didn't bother to add a separate example for explicit readonly propertie=
s,
>because I mainly regard
>readonly classes as a shorthand for adding the readonly modifier for all
>properties


My two cents: examples are cheap, misunderstandings are expensive=2E What =
you have now is like a test suite that only tests the happy path - the exam=
ple doesn't demonstrate any of the details of the RFC=2E It would be really=
 helpful to have an example, or a commented line of code in a bigger exampl=
e, for each of the things this RFC will let you do, and some that it *won't=
* let you do, even for things that seem obvious to you, because they might =
not be obvious to everyone=2E

Regards,

--=20
Rowan Tommins
[IMSoP]