Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109221
MIME-Version: 1.0
References: <1b781e1e-3f27-485b-ab47-5eeaf9496548@www.fastmail.com>
In-Reply-To: <1b781e1e-3f27-485b-ab47-5eeaf9496548@www.fastmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Sun, 22 Mar 2020 19:36:46 -0600
Message-ID: <CAAKU0u=B5LwjVaSk9u_MAuHb+qzaxSqnWdtZqtFS4fsD6dejpQ@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Improving PHP's Object Egonomics: A broad analysis
From: internals@lists.php.net ("Levi Morrison via internals")

> In short: I believe our biggest potential win is to focus on 3 RFCs:
>
> * Constructor Promotion
I would vote yes on this, assuming the implementation is sane.

> * Named parameters
This one is tricky -- there are tradeoffs of every approach I've seen
proposed. I have an idea for another way to address this space, but it
too has drawbacks; there's inherently no free lunch here, I think.

> * Compound Property Visibility
What is this last one? I searched for "compound" in the article, but
did not get many hits, none of which described what it actually _is_.