Re: Issues with readonly classes
| From: | Derick Rethans | Date: | Sun, 04 Sep 2022 12:06:19 +0000 |
| Subject: | Re: Issues with readonly classes | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-118560@lists.php.net to get a copy of this message | ||
On 4 September 2022 11:46:18 BST, Nicolas Grekas <nicolas.grekas+php@gmail.com> wrote:
>Hi Marco,
>
>IMO good as-is: can be relaxed later (8.3 or later), if anybody believes
>> it's a show-stopper.
>>
>Readonly classes don't really need to be lazy.
>>
>
>"Break things and move slow" doesn't feel right to me for the language.
It's a new keyword that you have to opt into. So it's not breaking anything. It just means
you might not be able to use it for your use case yet.
(and before you say that third party code might add it, you can just say you don't support it
yet).
cheers
Derick