Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112635
User-Agent: Cyrus-JMAP/3.3.1-61-gb52c239-fm-20201210.001-gb52c2396
Mime-Version: 1.0
Message-ID: <ea3ad019-22be-4a1a-8153-1e56b66e4389@www.fastmail.com>
In-Reply-To: <03108284-740a-4a5d-130f-15b2e67e9df9@mabe.berlin>
References: <1d0abb04-4987-43a9-85bc-bccc3bd6be9a@www.fastmail.com>
 <03108284-740a-4a5d-130f-15b2e67e9df9@mabe.berlin>
Date: Tue, 29 Dec 2020 09:38:01 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: =?UTF-8?Q?Re:_[PHP-DEV]_Analysis_of_property_visibility,_immutability,_a?=
 =?UTF-8?Q?nd_cloning_proposals?=
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Dec 29, 2020, at 2:26 AM, Marc wrote:
> 
> On 28.12.20 21:23, Larry Garfield wrote:
> > There's been a number of discussions of late around property visibility and how to make objects more immutable.  Since it seems to have been well-received in the past, I decided to do a complete analysis and context of the various things that have been floated about recently.
> >
> > The full writeup is here:
> >
> > https://peakd.com/hive-168588/@crell/object-properties-and-immutability
> >
> > I hope it proves stimulating, at least of discussion and not naps.
> >
> 
> Thanks for the nice write up Larry!
> 
> Is there a reason you didn't mention the proposal for immutable classes?
> (probably because it never went into a final RFC)
> 
> https://externals.io/message/94913#94913
> 
> https://externals.io/message/79180#79180

Two main reasons:

1) It's not been discussed recently (see how old the dates are on those messages), so I wasn't thinking about it.

2) An immutable class would in all practicality be the same as a class where all the properties are initonly (or writeonce, but that was already rejected).  So any arguments for/against initonly apply in aggregate to an immutable class.

--Larry Garfield