Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118424
To: "'php internals'" <internals@lists.php.net>
References: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com> <CAOWwgpmee-vfAWsPkiSu826ST_vt8Nkp1Kp=ALH5WdXh6=7G0Q@mail.gmail.com>
In-Reply-To: <CAOWwgpmee-vfAWsPkiSu826ST_vt8Nkp1Kp=ALH5WdXh6=7G0Q@mail.gmail.com>
Date: Fri, 12 Aug 2022 01:38:00 +0200
Message-ID: <0e6401d8addb$651ca9d0$2f55fd70$@webkr.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
Content-Language: de
Thread-Index: AQIYj4WUzxzLV9xtSCMZjUkct1AF5QGVaAZkrR3m0pA=
Subject: RE: [PHP-DEV] [RFC] Asymmetric visibility
From: andre@webkr.de (=?UTF-8?Q?Andr=C3=A9_H=C3=A4nsel?=)

 Nicolas Grekas wrote:

> But I'm also wondering about the use case where asymmetry would be
> useful in practice now that we have readonly?
> I voted against readonly at the time because it didn't address
> cloning, and also because it deprives end-users vs code authors IMHO
> (alike "final"). I would have very much prefered asymmetric
> visibility back then. But now that we are here, what are the use cases?

Isn't it (obviously?) to have setters that ensure all invariants of the
properties are met? I'd still rather have Property Accessors as
described in https://wiki.php.net/rfc/property_accessors, but I think
AV is a step in the right direction.

As for readonly, I don't understand why that exists at all. Yes, it's
good that readonly properties can only be set from within the class,
but only once, so you get setters that throw when called a second time,
which I think is very, VERY unexpected behavior. Calling them
"readonly" is also somewhat misleading because of course the objects
assigned to those "readonly" properties can still be mutated, they can
just not be reassigned.