Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119031
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1115-g8b801eadce-fm-20221102.001-g8b801ead
Mime-Version: 1.0
Message-ID: <411c8b54-78c2-4e67-91da-cd2f2dab88aa@app.fastmail.com>
In-Reply-To: 
 <CA+kxMuT2uXLy_GSiOa-XCHT5XE5xOHew7CkDev3obKjt7y08Qw@mail.gmail.com>
References: <0854b030-c51c-4c1b-a7dd-22835a1e5da9@app.fastmail.com>
 <CA+kxMuT2uXLy_GSiOa-XCHT5XE5xOHew7CkDev3obKjt7y08Qw@mail.gmail.com>
Date: Thu, 24 Nov 2022 18:07:14 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [RFC] Asymmetric Visibility, with readonly
From: larry@garfieldtech.com ("Larry Garfield")

On Sun, Nov 20, 2022, at 7:20 AM, Dan Ackroyd wrote:
> Hi Larry,
>
> Regarding the syntax, up until now PHP has only supported the letters
> a-z and underscore in keywords.
>
> I realise this is an aesthetic thing, but "private(set)" looks like a
> function to me, and not a keyword. I saw the previous poll, and it
> didn't include options for either protected_set/private_set or
> protectedset/privateset.
>
> Was there a technical reason for excluding them as an option?

Not in particular.  We originally proposed `private(set)` because that's what Swift uses.  In the discussion people proposed several alternatives that I put into the poll, but `private_set` wasn't one of them.  Although several people said they were opposed to parens in the keyword, the two options that had parens (`private(set)` and `pubilc(set: private)`) were the leaders for all rounds.  I was quite surprised at that, personally; I expected `private:set` to do a lot better under the circumstances.  But that's not how the poll played out.

--Larry Garfield