Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118386
MIME-Version: 1.0
References: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com>
In-Reply-To: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com>
Date: Mon, 8 Aug 2022 11:45:01 +0200
Message-ID: <CADK1yXKN9ndSx-JSRkxzwZ_Lx4yx=d7SpuE=y24LXPpCj_Dy2Q@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000096cd1405e5b7ad85"
Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility
From: deleugyn@gmail.com (Deleu)

--00000000000096cd1405e5b7ad85
Content-Type: text/plain; charset="UTF-8"

On Fri, Aug 5, 2022 at 7:09 PM Larry Garfield <larry@garfieldtech.com>
wrote:

> Ilija Tovilo and I are happy to present the first new RFC for PHP 8.3:
> Asymmetric Visibility.
>
> https://wiki.php.net/rfc/asymmetric-visibility
>
> Details are in the RFC, but it's largely a copy of Swift's support for the
> same.
>
> --
>   Larry Garfield
>   larry@garfieldtech.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>
Just wanted to point out that I loved syntax proposals by Juliette and
Mike. Any of them would be better. Making a better syntax for PHP would be
better than consistency with Swift, IMO.

But I'm also inclined to agree with Marco Pivetta that this change is a lot
less exciting now that we have `readonly`. In extremely rare cases where I
need to modify an attribute more than once, I just fallback to private +
getter and the nice thing about it is that it creates a consistent mindset
that if a property is being accessed via a getter, then the reader should
be advised that the property may change depending on WHEN it's accessed.

-- 
Marco Deleu

--00000000000096cd1405e5b7ad85--