Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119418
MIME-Version: 1.0
References: <CAH5C8xWg6bP86qBgK9NSxL+L8dQsijeYX_YwnyiCbddoL=FefA@mail.gmail.com>
 <CAJp_myXBrmghtCAHiMOH9R9+CAg5bMnu4qP-w=2GyUUXuXsyiQ@mail.gmail.com>
In-Reply-To: <CAJp_myXBrmghtCAHiMOH9R9+CAg5bMnu4qP-w=2GyUUXuXsyiQ@mail.gmail.com>
Date: Tue, 24 Jan 2023 16:13:35 +0100
Message-ID: <CAPzBOBP0Wh+xWvCZu8JigbS2KTc3-OCB7k3cJ8t8UUXvGqBF3w@mail.gmail.com>
To: "Matthew Weier O'Phinney" <mweierophinney@gmail.com>
Cc: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Vote] Readonly amendments
From: landers.robert@gmail.com (Robert Landers)

On Tue, Jan 24, 2023 at 3:27 PM Matthew Weier O'Phinney
<mweierophinney@gmail.com> wrote:
>
> On Tue, Jan 24, 2023 at 2:55 AM M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail=
.com> wrote:
>
> > Hi Everyone,
> >
> > We've just opened the vote for the "Readonly amendments" RFC, which is
> > going to be open for 2 weeks (until 2023-02-07).
> >
> > Link: https://wiki.php.net/rfc/readonly_amendments
> > Discussion: https://externals.io/message/119007
> >
>
> I missed something when reviewing previously.
>
> Under the Proposal 1 section is the following verbiage:
>
> > readonly classes can declare neither static, nor untyped properties, no
> matter if the declaration is done directly in the class or indirectly via=
 a
> trait (https://github.com/php/php-src/issues/9285). Under this RFC, their
> non-readonly child classes would support them as any other child class do=
es.
>
> However, the example demonstrates neither static nor untyped properties. =
As
> such, it's hard to understand what pattern you are trying to enable here.
> Could you provide an example of a child class that uses static and/or
> untyped properties, please? Basically trying to understand what this woul=
d
> enable, and why.
>
> --
> Matthew Weier O'Phinney
> mweierophinney@gmail.com
> https://mwop.net/
> he/him

Mocking