Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110792
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
In-Reply-To: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
Date: Tue, 30 Jun 2020 09:59:22 +0200
Message-ID: <CAF+90c9E4Aq9reaDFE2JhzzXHX9Qoi+DsDiyNFgDupFBA+pmuA@mail.gmail.com>
To: =?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?= <andre.romcke@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009dca5905a9488e4e"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000009dca5905a9488e4e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 29, 2020 at 11:43 AM Andr=C3=A9 R=C3=B8mcke <andre.romcke@gmail=
.com>
wrote:

> Good morning Internals,
>
> I'd like to start discussion on a new RFC proposing a way to be able to
> (optionally) specify property
> write visibility, separate from read:
>
> https://wiki.php.net/rfc/property_write_visibility
>
> This enables readonly, write-only and immutable like semantics for PHP's
> properties.
>
> These are the common use cases where users tend to resort to magic method=
s
> or setter/getter
> methods. This proposal will as such avoid unnecessary boilerplate, makes
> coding easier and more
> ergonomic, and in the case of magic method usage improve performance.
>

I think this is a good direction to explore, but would recommend delaying
it until PHP 8.1. As the RFC and discussion note, the design space here
overlaps significantly with both readonly/immutability and property
accessors. We should take enough time to consider these
alternatives/extensions as well, to ensure that we don't end up with
multiple distinct and possibly incompatible mechanisms. We don't have that
time before PHP 8.0 feature freeze.

Regards,
Nikita

--0000000000009dca5905a9488e4e--