Re: Re: Issues with readonly classes
| From: | Máté Kocsis | Date: | Tue, 20 Sep 2022 07:59:09 +0000 |
| Subject: | Re: Re: Issues with readonly classes | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-118668@lists.php.net to get a copy of this message | ||
Hi Nicolas, Larry,
Mate, WDYT?
>
When I was working on the readonly class RFC, I realized that the readonly
keyword very naturally fits services besides value objects. So my
expectation has been that until we can fix the issue with cloning, people
would mainly apply readonly to services. Not that it is very useful, but I
would also feel some kind of weird fulfillment by doing so.
Regarding cloning: I created a WIP PR not long ago to fix the
aforementioned cloning issue, and I'll pursue a readonly amendment RFC in
the coming weeks (or month) containing the long awaited improvements for
cloning (hopefully together with the "clone with" construct) and possibly
with this inheritance-related change Nicolas proposed, unless someone can
come up with an ultimate counter-argument.
Regards:
Máté