Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118210
MIME-Version: 1.0
References: <CAPyj-LBYp=CytZfkqaHmKQi9dGnk8p6sBZqb3qe7FjjJ_DbJsg@mail.gmail.com>
In-Reply-To: <CAPyj-LBYp=CytZfkqaHmKQi9dGnk8p6sBZqb3qe7FjjJ_DbJsg@mail.gmail.com>
Date: Wed, 6 Jul 2022 17:06:48 +0200
Message-ID: <CABdc3WpFTASVh_6UaGmws7tyXvCu+09zPMPhp5JFcYbf8Qr3xw@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001b26fe05e32452d6"
Subject: Re: [PHP-DEV] [RFC][Voting] Fetch properties of enums in const expressions
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--0000000000001b26fe05e32452d6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ilija,

pt., 1 lip 2022 o 15:03 Ilija Tovilo <tovilo.ilija@gmail.com> napisa=C5=82(=
a):

> Hi everyone
>
> I opened voting for the "Fetch properties of enums in const expressions"
> RFC.
> https://wiki.php.net/rfc/fetch_property_in_const_expressions


I voted NO because the originating problem this RFC tries to solve
described in
https://github.com/php/php-src/issues/8344 is easily solvable by aither
1. introducing a simple constant string value used in both places the enum
case and as an attribute value,
2. changing the attribute argument to enum instead.

Personally, I'd see using enums as array keys feature first instead (which
the RFC reminds
in its introductory section as not possible yet) before we start improving
places around enums.

Best regards,
Micha=C5=82 Marcin Brzuchalski

--0000000000001b26fe05e32452d6--