Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119434
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-107-g82c3c54364-fm-20230131.002-g82c3c543
Mime-Version: 1.0
Message-ID: <169937e8-f390-46a1-a6c2-e2294a95131c@app.fastmail.com>
In-Reply-To: 
 <CAH5C8xWsBsuzJ-7xwisUZxY+kxSmh-PhkAkPWh68c=qDs=nLrw@mail.gmail.com>
References: 
 <CAH5C8xWsBsuzJ-7xwisUZxY+kxSmh-PhkAkPWh68c=qDs=nLrw@mail.gmail.com>
Date: Tue, 31 Jan 2023 15:47:15 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Discussion] Typed class constants
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Jan 31, 2023, at 3:01 PM, M=C3=A1t=C3=A9 Kocsis wrote:
> Hi Everyone,
>
> A few years ago, Benas Seliuginas announced the "Typed constants" RFC (
> https://externals.io/message/110755) which apparently had a
> positive reception overall.
> Unfortunately, there were some issues with the implementation (namely,=
 with
> the parser)
> so the RFC was stuck.
>
> A few weeks ago, I reached out to Benas whether he intended to resurre=
ct
> the proposal, but
> due to time constraints, he couldn't, and was OK with me continuing it.
> With some help from
> Bob Weinand, I managed to overcome the implementation difficulties, and
> adapted it
> to the newly added type-related features.
>
> Please find the updated RFC here:
> https://wiki.php.net/rfc/typed_class_constants.
>
> Regards,
> M=C3=A1t=C3=A9

One question:

public const int TEST1 =3D C;

In context, is that supposed to be TEST =3D C?

That example in particular is very confusing to me; I don't actually gro=
k what it's even doing.

Aside from that, everything else looks good to me.

--Larry Garfield