Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118356
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: Fri, 5 Aug 2022 21:27:49 +0200
Message-ID: <CABdc3WqQ-kLTa3C=61_=yW-yJZuP2p_QW1TNe12WuHHur7aHng@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000da462805e583762f"
Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000da462805e583762f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Larry,

pt., 5 sie 2022, 19:09 u=C5=BCytkownik Larry Garfield <larry@garfieldtech.c=
om>
napisa=C5=82:

> 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 th=
e
> same.
>

Thanks for taking efforts on new RFC.

Why not C# style property accessors? It feels more natural for me while
Swift solution IMHO looks weird/odd composed with PHP class definition
syntax. The arguments in favor from the RFC look forcibly (couldn't find
better word).

Cheers,
Micha=C5=82 Marcin Brzuchalski

--000000000000da462805e583762f--