Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110776
Return-Path: <marandall@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 93235 invoked from network); 29 Jun 2020 15:21:47 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 29 Jun 2020 15:21:47 -0000
To: internals@lists.php.net
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
Date: Mon, 29 Jun 2020 15:10:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Posted-By: 87.81.129.66
Subject: Re: [RFC] Property write visibility
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-110776@news.php.net>

On 29/06/2020 10:41, André Rømcke wrote:
> https://wiki.php.net/rfc/property_write_visibility

I'd like this feature as a stop-gap for accessors.

However, I don't like the syntax at all, I couldn't reasonably vote for 
it in its current suggested state. I think it's just too messy.

I'm not sure what the alternative should be though. It seems like the 
accessor syntax would be the only long-term clean way.

Mark Randall