Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118363
MIME-Version: 1.0
References: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com>
 <CABdc3WqQ-kLTa3C=61_=yW-yJZuP2p_QW1TNe12WuHHur7aHng@mail.gmail.com>
 <e122e44f-550e-4089-8100-a27df9f8c9fa@www.fastmail.com> <CAKxcST_Mu3qDKKLgtsBBVAm=6mLirhjZ-88f+jjWeNhWyzO16A@mail.gmail.com>
 <A78DA1F7-1F74-4A94-962C-0EA5979431AD@gmail.com>
In-Reply-To: <A78DA1F7-1F74-4A94-962C-0EA5979431AD@gmail.com>
Date: Sun, 7 Aug 2022 12:54:12 +0200
Message-ID: <CANS-=pfq1Q+aK6CWTGKpiSH_M4PABQwb-65HqznDw_xzoDM8+Q@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000097b2c105e5a48651"
Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility
From: kjarli@gmail.com (Lynn)

--00000000000097b2c105e5a48651
Content-Type: text/plain; charset="UTF-8"

On Sun, Aug 7, 2022 at 12:34 PM Rowan Tommins <rowan.collins@gmail.com>
wrote:

> Can you expand on where you think the ambiguity / implicitness is? As I
> understand it, the RFC is proposing exactly three new combined access
> levels:
>
> - "public private(set)"
> - "public protected(set)"
> - "protected private(set)"
>
> Although aesthetically it will take a bit of getting used to, it seems to
> me pretty clear that the first means "mostly public, but private if you
> want to set it", and so on.
>
> The only thing I can think of that could be described as "implicit" is
> that accessing a property by reference is considered a "set" operation,
> which I'm not sure how any implementation could avoid.


Personally for me it's the syntax. Reading "public private", "public
protected", or "protected private" reads really weird `public private(set)
static self $property`. In the end it makes sense if you know what it
means, otherwise it's probably confusing. I really like this RFC and I feel
like this might just be the way to go forward, but I have my doubts about
how many more keywords can be realistically added before it becomes a
problem.

--00000000000097b2c105e5a48651--