Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119793
MIME-Version: 1.0
References: <CAJOtmejYbDktip6VK6HAVF97W4NJG4RUMX7GRc0gyi5BUpQWkA@mail.gmail.com>
 <080d1241-0956-41bf-aaf3-d9582cfce3ef@app.fastmail.com>
In-Reply-To: <080d1241-0956-41bf-aaf3-d9582cfce3ef@app.fastmail.com>
Date: Thu, 30 Mar 2023 17:21:10 +0300
Message-ID: <CAAwdEzDjaQUrL90VyXUHk4CpPu7UZ7ML24Z7=fu5_fkNocAR3A@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ded9c705f81ece04"
Subject: Re: [PHP-DEV] [RFC] Properties in interfaces
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--000000000000ded9c705f81ece04
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 30, 2023 at 3:50=E2=80=AFPM Larry Garfield <larry@garfieldtech.=
com>
wrote:

>
> This is a part of the "Property Hooks" RFC that Ilija and are working on.
> It's not *quite* done yet, but it's mostly there.  The draft is available
> here: https://wiki.php.net/rfc/property-hooks
>
>
Do you think we could have a smaller RFC that only deals with properties in
interfaces that are just like what's allowed in classes right now, public
and public readonly?
The need seems to be: a readonly property in classes and a interface that
signals a get-only access so maybe readonly flag on interface attribute is
clear.

Or maybe that can be attempted to be achieved in the same rfc and we
fallback to a smaller RFC for the interface only in cases property-hooks
RFC does not pass?

Thank you,
Alex

--000000000000ded9c705f81ece04--