Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115445
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
In-Reply-To: <CA+hqhpeWACWYp=VNj0=oWkpPa++uiRF+=VmN34ZVBUu1dQOXPw@mail.gmail.com>
Date: Fri, 16 Jul 2021 17:09:00 -0400
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E2359773-7E55-4A87-9136-D43AA3A0E52F@newclarity.net>
References: <CAM0CcxjJYYRrdzNjm285OQ6zDS8J7tqi0kLBeTGAP-2JXyqrDw@mail.gmail.com>
 <CA+hqhpeWACWYp=VNj0=oWkpPa++uiRF+=VmN34ZVBUu1dQOXPw@mail.gmail.com>
To: Bruce Weirdan <weirdan@gmail.com>
Subject: Re: [PHP-DEV] Readonly properties - immutability by default
From: mike@newclarity.net (Mike Schinkel)

> On Jul 16, 2021, at 6:12 AM, Bruce Weirdan <weirdan@gmail.com> wrote:
>=20
> On Fri, Jul 16, 2021 at 9:45 AM Eugene Sidelnyk <zsidelnik@gmail.com> =
wrote:
>=20
>> Readonly properties are really useful for DDD, where everything is =
going to
>> be immutable. It promotes best practices. However for people to use =
it,
>> syntax should be concise and brief.
>=20
> If every property of the class is readonly it would probably be better
> to declare that with a class modifier.
>=20
> E.g.
>=20
> ```php
> readonly class Entity {
>    public int $count;
>    public string $data;
> }
> ```

Having a "readonly" class where the properties are read-only by default =
makes sense to me, but maybe the better way to do it is with an =
attribute?

#[Readonly]
class Entity {
   public int $count;
   public string $data;
}

OTOH, that would be inconsistent with using `readonly` as a keyword for =
properties.=20

-Mike
P.S. Maybe readonly properties should be implemented with an attribute =
instead of a keyword?  But then that would be opening a can of worms...=