Re: [RFC] Asymmetric Visibility, with readonly
| From: | Derick Rethans | Date: | Mon, 14 Nov 2022 11:32:04 +0000 |
| Subject: | Re: [RFC] Asymmetric Visibility, with readonly | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119003@lists.php.net to get a copy of this message | ||
On Mon, 14 Nov 2022, Stephen Reay wrote:
> As I understand it, you’re suggesting that a property declared as
>
public protected(set) would never trigger __set().
I would think that that would be against our current practice, which is
easy enough to explain as "if the property isn't visible set,
then use __set()". I would argue that "protected(set)" marks a property
as invisible from a non-inherited class/method, and hence __set should
be called.
cheers,
Derick