Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110782
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
In-Reply-To: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
Date: Mon, 29 Jun 2020 17:44:16 +0200
Message-ID: <CADyq6sKXtrc4tb5ukBtxmNb9PqpRFP2R9MvGRfdwpuGGv-YJnQ@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="00000000000013bed405a93aefb4"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: ocramius@gmail.com (Marco Pivetta)

--00000000000013bed405a93aefb4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Andr=C3=A9,

This does indeed seem to cut into the traditional property accessors scope.

I'm no longer seeing a reason to have property accessors, since immutable
state (and promotion thereof) is much more relevant to fight bugs and
improve application performance and maintainability.

Therefore, I would endorse re-visiting the RFC at
https://wiki.php.net/rfc/write_once_properties instead.

M=C3=A1t=C3=A9 also linked today (
https://twitter.com/kocsismate90/status/1277625002720968704) that C# 9.0 is
getting init-only properties, which looks similar to the RFC linked above.

Assuming we solve annoyances around cloning, that would be a more sensible
way forward, while property accessors seem to perpetuate the bad practice
of getters and setters, which are the main cause for me having to fire up a
debugger in any environment.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Mon, Jun 29, 2020 at 11:42 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.
>
>
> Best,
> Andr=C3=A9 R=C3=B8mcke
>

--00000000000013bed405a93aefb4--