Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109222
MIME-Version: 1.0
References: <1b781e1e-3f27-485b-ab47-5eeaf9496548@www.fastmail.com>
In-Reply-To: <1b781e1e-3f27-485b-ab47-5eeaf9496548@www.fastmail.com>
Date: Mon, 23 Mar 2020 06:55:14 +0100
Message-ID: <CABdc3Wr4EnO4XwDhUqn976azYE2YsuH0-SHkre81eDNOP-Y8_g@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001edcb105a17f48da"
Subject: Re: [PHP-DEV] Improving PHP's Object Egonomics: A broad analysis
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--0000000000001edcb105a17f48da
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Larry,

pon., 23 mar 2020, 01:48 u=C5=BCytkownik Larry Garfield <larry@garfieldtech=
.com>
napisa=C5=82:

> Hi folks.
>
> There have been a lot of RFCs and possible RFCs of late that are all
> circling around the same related problem space: Working with objects righ=
t
> now involves too much boilerplate to get things done.  As I've mentioned
> several times, I believe we need to be looking for broader solutions rath=
er
> than narrowly-focused one-offs.
>
> To that end, I have written an extensive analysis of the problem space an=
d
> the current and recent proposals.  I've put it on my blog rather than
> inline here because it's quite long and the blog offers better formatting=
.
>
> Discussion can happen here, but I'll also respond to comments there.
>
> In short: I believe our biggest potential win is to focus on 3 RFCs:
>
> * Constructor Promotion
>

That still doesn't resolve issue with lot of boilerplate when you deal with
small objects for which public readonly is enough like object-initializer
could. So I'm not sure about my vote here. It does solve only one narrow
situation for me.

* Named parameters
>

What would be nice for methods and functions. +1

* Compound Property Visibility
>

I didn't get it what benefits over property accessors it could have.


> For details, see the full writeup:
>
> https://hive.blog/php/@crell/improving-php-s-object-ergonomics
>
> Thank you for your attention.
>
> --
>   Larry Garfield
>   larry@garfieldtech.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000001edcb105a17f48da--